View QT60161B-AS_1070052.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

l q qt60161b 16 k ey qmatrix ? k eypanel s ensor ic advanced second generation qmatrix controller 16 touch keys through any dielectric 100% autocal for life - no adjustments required spi slave or master/slave interface to a host controller parallel scan interface for electromechanical compatibility keys individually adjustable for sensitivity, response time, and many other critical parameters sleep mode with wake pin synchronous noise suppression mix and match key sizes & shapes in one panel adjacent key suppression feature panel thicknesses to 5 cm or more low overhead communications protocol 44-pin tqfp package applications - automotive panels machine tools atm machines touch-screens appliance controls outdoor keypads security keypanels industrial keyboards the qt60161b digital charge-transfer (qt) qmatrix? ic is designed to detect human touch on up 16 keys when used in conjunction with a scanned, passive x-y matrix. it will project the keys through almost any dielectric, e.g. glass, plastic, st one, ceramic, and even wood, up to thicknesses of 5 cm or more. the touch areas are defined as simple 2-part interdigitated electrodes of conductive material, like copper or screened silver or carbon deposited on the rear of a control panel. key sizes , shapes and placement are almost entirely arbitrary; sizes and shapes of keys can be mixed within a single panel of keys and can vary by a factor of 20:1 in surface area. the sensitivity of each key can be set individually via simple functions over the spi or uart port, for example via quantums qmbtn program, or from a host microcontroller. key setups are stored in an onboard eeprom and do not need to be reloaded with each powerup. the device is designed specifically for appliances, electronic kiosks, security panels, portable instruments, machine tools, or similar products that are subject to environmental influences or even vandalism. it can permit the construction of 100% sealed, watertight control panels that are immune to humidity, temperature, dirt accumulation, or the physical deterioration of the pan el surface from abrasion, chemicals, or abuse. to this end the device contains quantum-pioneered adaptive auto self-calibration, drift compensation, and digital filtering algorithms that make the sensing function robust and survivable. the part can scan matrix touch keys over lcd panels or other displays when used with clear ito electrodes arranged in a matrix. it does not require 'chip on glass' or other exotic fabrication techniques, thus allowing the oem to source the matrix from mul tiple vendors. materials such as such common pcb materials or flex circuits can be used. external circuitry consists of a resonator and a few capacitors and resistors, all of which can fit into a footprint of less th an 6 sq. cm (1 sq. in). control and data transfer is via either a spi or uart port; a parallel scan port provides backwards compatibility with scanned electromechanical keys. the qt60161b makes use of an important new variant of charge-transfer sensing, transverse charge-transfer, in a matrix format that minimizes the number of required scan lines. unlike some older technologies it does not require one sensing ic per key. the qt60161b is identical to earlier qt60161 in all respects except that the device exhibits lower signal noise. this device replaces qt60161 parts directly. after december 2003 the qt60161 will no longer be sold. lq copyright ? 2001 quantum research group ltd pat pend. r1.03/04.03 QT60161B-AS -40 0 c to +105 0 c tqfp part number t a available options ss so vref drdy led vss vdd cs0a cs0b cs1a cs1b smp x0opa x1opb x2 x3 vdd vss xs0 xs1 xs2 xs3 mosi miso sck rst vdd vss xto xti rx tx ws ys0 ys1 ys2 ys3 avdd agnd aref cs3b cs3a cs2b cs2a 1 2 3 4 5 6 7 8 9 10 11 23 24 25 26 27 28 29 30 31 32 33 44 43 42 41 40 39 38 37 36 34 35 12 13 14 22 21 19 20 18 17 16 15 qt60161b tqfp-44
18 y 0x79 - column keys scope ........................... 18 x 0x78 - row keys scope ............................. 18 s 0x53 - all keys scope .............................. 18 s 0x73 - specific key scope ........................... 18 5.2 scope commands .............................. 17 p 0x70 - put command .............................. 17 g 0x67 - get command .............................. 17 5.1 put / get direction commands ..................... 17 5 commands & functions ............................. 16 4.8 eeprom corruption .............................. 15 4.7 parallel scan port ............................... 15 4.6 sensor echo and data response .................. 14 4.5 uart interface ................................. 13 4.4 spi master-slave mode .......................... 12 4.3 spi slave-only mode ............................ 12 4.2 spi port specifications ........................... 11 4.1 serial protocol overview .......................... 11 4 communications interfaces .......................... 11 3.18 esd / noise considerations ...................... 11 3.17 power supply & pcb layout ..................... 11 3.16 oscilloscope sync .............................. 10 3.15 led / alert output .............................. 9 3.14 sleep_wake / noise sync pin (ws) ................. 9 3.13 startup / calibration times ......................... 9 3.12 oscillator ....................................... 9 3.11 reset input ..................................... 9 3.10 water film suppression ........................... 9 3.9 sample capacitors ................................ 9 3.8 burst spacing .................................... 9 3.7 intra-burst spacing ................................ 8 3.6 burst acquisition duration .......................... 8 3.5 burst length & sensitivity ........................... 8 3.4.2 noise coupling into y lines ............................ 8 3.4.1 rfi from y lines .................................. 8 3.4 'y' gate drives .................................... 8 3.3.2 noise coupling into x lines ............................ 8 3.3.1 rfi from x lines .................................. 8 3.3 'x' electrode drives ................................ 7 3.2 signal path ...................................... 7 3.1 matrix scan sequence ............................. 7 3 circuit operation ..................................... 7 2.11 device status & reporting ......................... 7 2.10 full recalibration ................................. 6 2.9 adjacent key suppression (?aks?) .................... 6 2.8 reference guardbanding ........................... 6 2.7 positive recalibration delay ......................... 6 2.6 detection integrator ................................ 6 2.5 negative recalibration delay ........................ 5 2.4 drift compensation ................................ 5 2.3 hysteresis ....................................... 5 2.2 positive threshold ................................. 5 2.1 negative threshold ................................ 5 2 signal processing .................................... 4 1.3 communications .................................. 4 1.2 circuit overview .................................. 4 1.1 field flows ....................................... 4 1 overview ............................................ 34 8 index ............................................. 33 7.2 marking ....................................... 33 7.1 dimensions .................................... 33 7 mechanical ........................................ 32 6.5 maximum drdy response delays .................. 31 6.4 protocol timing ................................. 31 6.3 dc specifications ............................... 31 6.2 recommended operating conditions ................ 31 6.1 absolute maximum specifications .................. 31 6 electrical specifications ............................ 30 5.8 erratta / notes ................................. 30 5.7 timing limitations .............................. 27 5.6 function summary table ......................... 26 ^w 0x17 - noise sync ............................... 26 ^r 0x12 - oscilloscope sync ........................... 25 ^q 0x11 - data rate selection .......................... 25 z 0x5a - enter sleep ................................ 25 w 0x57 - return part signature ......................... 25 v 0x56 - return part version ........................... 25 r 0x72 - reset device ............................... 25 l 0x6c - return last command character ................... 24 b 0x62 - recalibrate keys ............................. 24 l 0x4c - lock reference levels ......................... 24 6 0x36 - eeprom checksum ........................... 24 5.5 supervisory / system functions .................... 24 ^p 0x10 - adjacent key suppression (?aks?) .................. 23 ^o 0x0f - negative reference error band ................... 23 ^n 0x0e - positive reference error band .................... 23 ^m 0x0d - intra-burst pulse spacing ....................... 23 ^l 0x0c - negative recalibration delay ..................... 23 ^k 0x0b - positive recalibration delay ..................... 22 ^j 0x0a - negative detect integrator limit ................... 22 ^i 0x09 - positive drift compensation rate .................. 22 ^h 0x08 - negative drift compensation rate5 ................. 22 ^g 0x07 - burst spacing .............................. 21 ^f 0x06 - burst length ............................... 21 ^d 0x04 - positive threshold hysteresis ..................... 21 ^c 0x03 - negative threshold hysteresis .................... 21 ^b 0x02 - positive detect threshold ....................... 21 ^a 0x01 - negative detect threshold ....................... 21 5.4 setup commands .............................. 20 k 0x6b - reporting of first touched key .................... 20 e 0x45 - error codes for group ......................... 19 e 0x65 - error code for selected key ...................... 19 % 0x25 - detect integrator counts for group ................. 19 " 0x22 - reference levels for group ...................... 19 ! 0x21 - delta signals for group ......................... 19 0x20 - signal levels for group ....................... 19 7 0x37 - general device status .......................... 18 6 0x36 - eeprom checksum ........................... 18 5 0x35 - detection integrator counts ...................... 18 2 0x32 - reference value ............................. 18 1 0x31 - delta signal for single key ....................... 18 0 0x30 - signal for single key .......................... 18 5.3 status commands ............................... ?quantum research group ltd. lq ii www.qprox.com qt60161b / r1.03 contents
table 1.1 device pin lis t slave select for spi direction control; active low i/o od ss 44 oscilloscope sync output o pp so 43 vref input for conversion reference i vref 42 data ready output for slave spi mode; active low o od drdy 41 active low led status drive / activity indicator o pp led 40 ground pwr vss 39 +5 supply pwr vdd 38 cs0 control a i/o pp cs0a 37 cs0 control b i/o pp cs0b 36 cs1 control a i/o pp cs1a 35 cs1 control b i/o pp cs1b 34 cs2 control a i/o pp cs2a 33 cs2 control b i/o pp cs2b 32 cs3 control a i/o pp cs3a 31 cs3 control b i/o pp cs3b 30 +5 supply for analog sections pwr aref 29 analog ground pwr agnd 28 +5 supply for analog sections pwr avdd 27 ys3 scan output line o pp ys3 26 ys2 scan output line o pp ys2 25 ys1 scan output line o pp ys1 24 ys0 scan output line o pp ys0 23 xs3 scan input line i xs3 22 xs2 scan input line i xs2 21 xs1 scan input line i xs1 20 xs0 scan input line i xs0 19 ground pwr vss 18 +5v supply pwr vdd 17 x3 drive matrix scan o pp x3 16 x2 drive matrix scan o pp x2 15 x1 drive matrix scan / communications option b input i/o pp x1opb 14 x0 drive matrix scan / communications option a input i/o pp x0opa 13 sample output control o pp smp 12 wake from sleep / sync to noise source i ws 11 uart transmit output o pp tx 10 uart receive input i rx 9 oscillator drive input. connect to resonator or crystal, or external clock source. i xti 8 oscillator drive output. connect to resonator or crystal.ply o pp xto 7 ground pwr vss 6 +5v supply pwr vdd 5 reset input, active low reset i rst 4 spi clock. in master mode is an output; in slave mode is an input i/o pp sck 3 master-in / slave out spi line. not used in master/slave spi mode. in slave mode outputs data to host (out only). i/o pp miso 2 master-out / slave in spi line. in master/slave spi mode is used for both communication directions. in slave spi mode is the data input (in only). i/o pp mosi 1 description type name pin i/o: i = input o = output pwr = power pin i/o = bidirectional line pp = push pull output drive od = open drain output drive ?quantum research group ltd. lq iii www.qprox.com qt60161b / r1.03
1 overview qmatrix devices are digital burst mode charge-transfer (qt) sensors designed specifically for matrix geometry touch controls; they include all signal processing functions necessary to provide stable sensing under a wide variety of changing conditions. only a few low cost external parts are required for operation. the entire circuit can be built in under 6 square centimeters of pcb area. the device has a wide dynamic range that allows for a wide variety of key sizes and shapes to be mixed together in a single touch panel. these features permit new types of keypad features such as touch-sliders, back-illuminated keys, and complex warped panels. the devices use an spi interface running at up to 3mhz rates to allow key data to be extracted and to permit individual key parameter setup, or, a uart port which can run at rates to 57.6 kbaud. the serial interface protocol uses simple commands; the command structure is designed to minimize the amount of data traffic while maximizing the amount of information conveyed. in addition to normal operating and setup functions the device can also report back actual signal strengths and error codes over the serial interfaces. qmbtn software for the pc can be used to program the ic as well as read back key status and signal levels in real time. a parallel scan port is also provided that can be used to directly replace membrane type keypads. qmatrix technology employs transverse charge-transfer ('qt') sensing, a new technology that senses the changes in an electrical charge forced across an electrode set. 1.1 field flows figure 1-1 shows how charge is transferred across an electrode set to permeate the overlying panel material; this charge flow exhibits a high dq/dt during the edge transitions of the x drive pulse. the charge driven by the x electrode is partly received onto the corresponding y electrode which is then processed. the part uses 4 'x' edge-driven rows and 4 'y' sense columns to sense up to 16 keys. the charge flows are absorbed by the touch of a human finger (figure 1-1) resulting in a decrease in coupling from x to y. thus, received signals decrease or go negative with respect to the reference level during a touch. as shown in figure 1-3, water films cause the coupled fields to increase slightly, making them easy to distinguish from touch. 1.2 circuit overview a basic circuit diagram is shown in figure 1-5. the x drives are sequentially pulsed in groupings of bursts. at the intersection of each x and y line in the matrix itself, where a key is desired, should be an interdigitated electrode set similar to those shown in figure 1-4. see quantum app note an-kd01, or consult quantum for application assistance. the device uses fixed external capacitors to acquire charge from the matrix during a burst of charge-transfer cycles; the burst length can be varied to permit digitally variable key signal gains. the charge is converted to digital using a single-slope conversion process. burst mode operation permits the use of a passive matrix, reduces rf emissions, and provides excellent response times. refer to section 3 for more details on circuit operation. 1.3 communications the device uses two variants of spi communications, slave-only and master-slave, a uart interface, plus a parallel scan interface. over the serial interfaces are used a command and data transfer structure designed for high levels of flexibility using minimal numbers of bytes. for more information see sections 4 and 5. the parallel scan port permits the replacement of electromechanical keypads that would be scanned by a microcontroller; the scan interface mimics an electromechanical keyboard s response. ?quantum research group ltd. l q 4 www.qprox.com qt60161b / r1.03 figure 1-2 field flows when touched figure 1-3 fields with a conductive film overlying panel x element y element figure 1-4 sample electrode geometries parallel lines serpentine spiral figure 1-1 field flow between x and y elements overlying panel x element y element
2 signal processing the device calibrates and processes signals using a number of algorithms specifically designed to provide for high survivability in the face of adverse environmental challenges. the qt60161b provides a large number of processing options which can be user-selected to implement very flexible, robust keypanel solutions. 2.1 negative threshold see also command ^a, page 21 the negative threshold value is established relative to a key s signal reference value. the threshold is used to determine key touch when crossed by a negative-going signal swing after having been filtered by the detection integrator (section 2.6). larger absolute values of threshold desensitize keys since the signal must travel farther in order to cross the threshold level. conversely, lower thresholds make keys more sensitive. as cx and cs drift, the reference point drift-compensates for these changes at a user-settable rate (section 2.4); the threshold level is recomputed whenever the reference point moves, and thus it also is drift compensated. the threshold is user-programmed on a per-key basis using the setup process (section 5). 2.2 positive threshold see also command ^b, page 21 the positive threshold is used to provide a mechanism for recalibration of the reference point when a key's signal moves abruptly to the positive. these transitions are described more fully in section 2.7. the threshold is user-programmed using the setup process described in section 5 on a per-key basis. 2.3 hysteresis see also command ^c and ^d, page 21 refer to figure 1-6. the qt60161b employs programmable hysteresis levels of 12.5%, 25%, or 50% of the delta between the reference and threshold levels. there are different hysteresis settings for positive and negative thresholds which can be set by the user. the percentage refers to the distance between the reference level and the threshold at which the detection will drop out. a percentage of 12.5% is less hysteresis than 25%, and the 12.5% hysteresis point is closer to the threshold level than to the reference level. the hysteresis levels are set for all keys only; it is not possible to set the hysteresis differently from key to key on either the positive or negative hysteresis levels. 2.4 drift compensation see also command s ^h, ^i, page 22 signal levels can drift because of changes in cx and cs over time. it is crucial that such drift be compensated, else false detections, non- detections, and sensitivity shifts will follow. the qt60161b can compensate for drift using two setups, ^h and ^i. drift compensation is performed by making the reference level track the raw signal at a slow rate, but only while there is no detection in effect. the rate of adjustment must be performed slowly, otherwise legitimate detections could be ignored. the devices drift compensate using a slew-rate limited change to the reference level; the threshold and hysteresis values are slaved to this reference. when a finger is sensed, the signal falls since the human body acts to absorb charge from the cross-coupling between x and y lines. an isolated, untouched foreign object (a coin, or a water film) will cause the signal to rise very slightly due to the enhanced coupling thus created. these effects are contrary to the way most capacitive sensors operate. once a finger is sensed, the drift compensation mechanism ceases since the signal is legitimately detecting an object. drift compensation only works when the key signal in question has not crossed the negative threshold level (section 2.1). the drift compensation mechanism can be made asymmetric if desired; the drift-compensation can be made to occur in one direction faster than it does in the other simply by setting ^h and ^i to different settings. ?quantum research group ltd. l q 5 www.qprox.com qt60161b / r1.03 figure 1-5 circuit block diagram x0 x1 x2 x3 y0 y1 y2 y3 keymatrix qt60161 spi to host x0 x1 x2 x3 cs0a cs0b sample cs0 sample caps cs1a cs1b cs2a cs2b cs3a cs3b cs1 cs2 cs3 uart to host scan input scan output vref reset wake / sync v cc opt a opt b led scope sync figure 1-6 detection and drift compensation threshold signal hysteresis reference output
drift compensation should usually be set to compensate faster for increasing signals than for decreasing signals. decreasing signals should not be compensated quickly, since an approaching finger could be compensated for partially or entirely before even touching the touch pad. however, an obstruction over the sense pad, for which the sensor has already made full allowance for, could suddenly be removed leaving the sensor with an artificially suppressed reference level and thus become insensitive to touch. in this case, the sensor should compensate for the object's removal by raising the reference level quickly. the drift compensation rate can be set for each key individually, and can also be disabled completely if desired on a per-key basis. drift compensation and the detection time-outs (section 2.5) work together to provide for robust, adaptive sensing. the time-outs provide abrupt changes in reference location depending on the duration of the signal 'event'. 2.5 negative recalibration delay see also command ^l, page 23 if a foreign object contacts a key the key's signal may change enough in the negative direction, the same as a normal touch, to create an unintended detection. when this happens it is usually desirable to cause the key to be recalibrated in order to restore its function after a time delay of some seconds. the negative recal delay timer monitors this detection duration; if a detection event exceeds the timer's setting, the key will be recalibrated so that it can function thereafter. the ^l function can be altered on a key by key basis. it can be disabled if desired by setting the ^l parameter to zero, so that it will never recalibrate automatically. 2.6 detection integrator see also command ^j, page 22 to suppress false detections caused by spurious events like electrical noise, the qt60161b incorporates a 'detection integrator' counter that increments with each detection sample until a user-defined limit is reached, at which point a detection is confirmed. if no detection is sensed on any of the samples prior to the final count, the counter is reset immediately to zero, forcing the process to restart. when an active key is released, the counter must count down to zero before the key state is set to 'off'. setting a key s detection integrator target value to zero disables that key although the bursts for that key continue normally. the detection integrator is extremely effective at reducing false detections at the expense of slower reaction times. in some applications a slow reaction time is desirable; the detection integrator can be used to intentionally slow down touch response in order to require the user to touch longer to operate the key. there are 16 possible values for this function. 2.7 positive recalibration delay see also command ^k, page 23 a recalibration can occur automatically if the signal swings more positive than the positive threshold level. this condition can occur if there is positive drift but insufficient positive drift compensation, or if the reference moved negative due to a recalibration, and thereafter the signal returned to normal. as an example of the latter, if a foreign object or a finger contacts a key for period longer than the negative recal delay, the key is recalibrated to a new lower reference level. then, when the condition causing the negative swing ceases to exist (e.g. the object is removed) the signal can suddenly swing back positive to near its normal reference. it is almost always desirable in these cases to cause the key to recalibrate to the new signal level so as to restore normal touch operation. the device accomplishes this by simply setting reference = signal. the time required to detect this condition before recalibrating is governed by the positive recalibration delay command. in order for this feature to operate, the signal must rise through the positive threshold level (section 2.2) for the proscribed interval determined by setup ^k. after the positive recal delay interval has expired and the fast-recalibration has taken place, the affected key will once again function normally. this interval can be set on a per-key basis; it can also be disabled by setting ^k to zero. 2.8 reference guardbanding see also command s ^n, ^o, page 23; ?l?, page 24 the qt60161b provides for a method of self-checking that allows the host to ascertain whether one or more key reference levels are 'out of spec'. this feature can be used to determine if an x or y line has broken, the matrix panel has delaminated from the control panel, or there is a circuit fault. reference guardbanding alerts the host when the reference level of a key falls outside of user-defined levels. the reference guardband is determined as a percent deviation from the 'locked' reference level for each individual key. these reference levels can be stored into internal eeprom via the lock command 'l' during production; deviations in reference levels that fall outside the guardbands centered on these locked reference levels are then reported as key errors. the amount of guardbanding can be set differently for each signal direction relative to the stored and locked levels. the possible settings are from 0.1% to 25.5% of signal reference in steps of 0.1% as set by commands ^n (positive swings) and ^o (negative swings). a setting of 0 (zero) disables the corresponding guardband direction. once the l command has recorded all values of signal reference into eeprom, and if guardbanding is enabled, the part will compare the actual reference level of each key to its corresponding guardbands to see if it falls outside of these limits. if so, either of bits 2 and 3 of command 'e' will be set for that key. the error will also appear in a bitfield reported via command 'e'. 2.9 adjacent key suppression (?aks?) see also command ^p, page 24 the qt60161b incorporates adjacent key suppression ( aks ) that can be enabled on a per-key basis. aks permits ?quantum research group ltd. l q 6 www.qprox.com qt60161b / r1.03
the suppression of multiple key presses based on relative signal strengths. aks assists in solving the problem of surface water which can bridge a key touch to an adjacent key, causing multiple key presses, causing multiple key presses even though only one key was touched. this feature is also useful for panels with tightly spaced keys, where a fingertip can partially overlap an adjacent key. aks works for keys that are aks-enabled anywhere in the matrix and is not restricted to physically adjacent keys; the device has no knowledge of which keys are physically adjacent. when enabled for a key, adjacent key suppression causes detections on that key to be suppressed if any other aks-enabled key in the panel has a more negative signal deviation from its reference. this feature does not account for varying key gains (burst length) but ignores the actual negative detection threshold setting for the key. if aks-enabled keys in a panel have different sizes, it may be necessary to reduce the gains of larger keys relative to smaller ones to equalize the effects of aks. the signal threshold of the larger keys can be altered to compensate for this without causing problems with key suppression. aks works to augment the natural moisture suppression capabilities of the device (section 3.10), creating a more robust touch panel. 2.10 full recalibration see also command ? b ? , page 24 the part fully recalibrates one or more keys after the b command has been issued to it, depending on the current scope of the b command. the device recalibrates all keys on powerup, after a hard reset via the rst pin or on power up, or via a reset using the r command. since the circuit tolerates a very wide dynamic signal range, it is capable of adapting to a wide mix of key sizes and shapes having widely varying cx coupling capacitances. if a false calibration occurs due to a key touch or foreign object on the keys during powerup, the affected key will recalibrate again when the object is removed depending on the settings of positive threshold and positive recal delay (sections 2.2 and 2.7). calibration requires 9 full burst cycles to complete, and so the time it takes is dependent on the burst spacing parameter (section 3.8 also, ^g, page 22. 2.11 device status & reporting see also commands ? 7 ? , page 19; ? e ? , page 19 ; e , page 20 ; k , page 20, k , page 20 the device can report on the general device status or specific key states including touches and error conditions, depending on the command used. usually it is most efficient to periodically request the general device status using command 7 first, as the response to this command is a single byte which reports back on behalf of all keys. 7 indicates if there are any keys detecting, calibrating, or in error. if command 7 reports a condition requiring further investigation, the host device can then use commands e , e , k or k to provide further details of the event(s) in progress. this hierarchical approach provides for a concise information flow using minimal data transfers and low host software overhead. 3 circuit operation a qt60161b reference circuit is shown in figure 2-1. 3.1 matrix scan sequence the circuit operates by scanning each key sequentially, key by key. key scanning begins with location x=0 / y=0. x axis keys are known as rows while y axis keys are referred to as columns . keys are scanned sequentially by row, for example the sequence y0x0 y0x1 y0x2 y0x3 y1x0 etc. each key is sampled from 1 to 64 times in a burst whose length is determined by setup ^f. a burst is completed entirely before the next key is sampled; at the end of each burst the resulting analog signal is converted to digital using a single-slope conversion process. the length of the burst directly impacts on the gain of the key; each key can have a unique burst length in order to allow tailoring of key sensitivity on a key by key basis. 3.2 signal path refer to figures 1-5, 3-1, and 3-2. x-drives. the x drives are push-pull cmos lines which drive charge through the matrix keys on the positive and negative edges of x. only the positive edge of x is used for signal purposes, however the negative edge must cause the charge across the keys to neutralize prior to the next positive edge, else the sampling mechanism will cease after one pulse. the part accomplishes this by holding all y lines to ground during the falling edge of x. charge gate. only one x row is pulsed during a burst. charge is coupled across a key's cx capacitance from the x row to all y columns. a particular key is chosen by gating the charge from a single y column into a single one of four possible sampler capacitors. the other three x and three y lines are clamped to ground during this process. dwell time. the dwell time is determined internally and is the same as one oscillator period, i.e. 83.3ns with a 12mhz resonator. the dwell time is set via internal switching action ?quantum research group ltd. l q 7 www.qprox.com qt60161b / r1.03 figure 3-1 qt60161b circuit model x drive (1 of 4) y line (1 of 4) x electrode y electrode cx cs (1 of 4) single-slope 14 bit adc burst control done start result smp csb csa rs (1 of 4) x
which limits the interval during which charge can be accepted by a cs capacitor after the rise of an x drive line. dwell time has a dramatic effect on the suppression of moisture films as described in section 3.10. cs charge integrator capacitor. the cs capacitors integrate charge arriving through the matrix keys' cx capacitances, correspondent with the rise of x; to do this a switching arrangement on the cs control pins permits the charge to accumulate so that the b side of the cs capacitors becomes negative when the a side is clamped to ground. charge conversion. at the end of each burst the voltage on cs is converted to digital by means of a single-slope conversion process, using one of the external resistors to ramp up the capacitor towards a reference voltage. the elapsed time required to reach the comparison voltage is the digital result. the time required to perform the conversion depends on cs, cx, rs, aref, and the burst length. 3.3 'x' electrode drives the 'x' lines are directly connected to the matrix without buffering. the positive edges of these signals are used to create the transient field flows used to scan the keys. only one x line is actively driving the matrix for scanning purposes at a time, and it will pulse repetitively for a burst length for each key as determined by the 'burst length' setups parameter (see command ^f, page 21 and section 3.5). 3.3.1 rfi f rom x l ines x drive lines will radiate a small amount of rfi. this can be attenuated if required by using series resistor in-line with each x trace; the resistor should be placed near to the qt60161b. typical values can range from 100 to 500 ohms. excessive amounts of r will cause a counterproductive drop in signal strength. rc networks can also be used as shown in figure 4-6. resistance in the x lines also have the positive effect of limiting esd discharge currents (section 3.18). 3.3.2 n oise c oupling i nto x lines external noise, sometimes caused by ground bounce due to injected line noise, can couple into the x lines and cause signal interference in extreme cases. such noise can be readily suppressed by the use of series resistors as described above. adding a small capacitor to the matrix line on the qt60161b side of the r, for example 100pf to ground near the qt60161b, will greatly help to reduce such effects. 3.4 'y' gate drives there are 4 'y' gate drive pairs (cs0a,b..cs3a,b); only one pair of these lines is used during a burst for a particular key. the magnitude of the voltages accumulated on the cs capacitors should never exceed 0.25v. 3.4.1 rfi f rom y l ines y lines are nearly 'virtual grounds' and are negligible radiators of rfi; in fact, they act as sinks for rfi emitted by the x lines. resistors are not required in the y lines for rfi suppression, and in fact can introduce cross-talk among keys if large enough. however, small resistance values can be beneficial to limit esd transients and make the circuit more resistant to external rf fields (section 3.18). 3.4.2 n oise c oupling i nto y l ines external noise, sometimes caused by ground bounce due to power line noise, can couple into the y lines and cause signal interference in extreme cases. such noise can be readily suppressed by adding a 22pf capacitor from each y line to ground near the qt60161b. 3.5 burst length & sensitivity see also command ^f, page 21 the signal gain in volts / pf of cx for each key is controlled by circuit parameters as well as the burst length. the burst length is simply the number of times the charge-transfer ( qt ) process is performed on a given key. each qt process is simply the pulsing of an x line once, with a corresponding y line gated so as to capture the resulting charge passed through the key s capacitance cx. qt60161b devices use a finite number of qt cycles which are executed in a short burst. there can be from 1 to 64 qt cycles in a burst, in accordance with the list of permissible values shown on page 21. if a key's burst length is set to zero, that burst is disabled but its time slot in the scanning sequence of all keys is preserved so as to maintain scan timing. increasing burst length directly affects key sensitivity. this occurs because the accumulation of charge on cs is directly linked to the burst length. the burst length of each key can be set individually, allowing for direct digital control over the signal gains of each key, indivudally. apparent touch sensitivity is also controlled by the negative threshold setting (section 2.1). burst length and negative threshold interact; normally burst lengths should be kept as short as possible to limit rf emissions, but the threshold setting should normally be kept above a setting of 6 to limit false detections. the detection integrator can also prevent false detections at the expense of slower reaction times (section 2.6). the value of rs also affects sensitivity. higher values of rs will lead to larger values of adc result and higher conversion gains. the side effect of this is that the conversion will take longer and timing conflicts can occur (section 3.6). cs does not significantly affect gain . smaller values of cs will have higher delta signal voltages but this gain increase is offset by the decrease in gain caused by a steeper adc conversion slope. however smaller values of cs lead to faster conversion times for a given value of rs, which in turn allows for more relaxed burst timings. smaller values of cs also reduce the dynamic range of the system, meaning that the acquisition becomes less tolerant of high values of cx, due to earlier saturation of the voltage across cs. 3.6 burst acquisition duration the total time required to acquire a key's signal depends on the burst length for that key plus the time required to convert the voltage on the corresponding cs capacitor to digital. the conversion is performed via a single-slope adc process using one of the external rs resistors. if the total time required for the acquisition, i.e. the burst length plus adc times plus the signal processing and serial interface command handler times exceed the burst spacing setup parameter (section 3.8), significant timing errors and communications problems can occur. the time taken by the burst itself is straightforward to quantify, but the time required to do the adc step is not. the adc step depends on the value of vref (pin 42), cs, rs, and ?quantum research group ltd. l q 8 www.qprox.com qt60161b / r1.03
cx. therefore it is vital that the circuit be checked with an oscilloscope to make sure that burst spacings are unaffected during normal operation. 3.7 intra-burst spacing see also command ^m, page 23 the time between x drive pulses during a burst is the intra-burst pulse qt spacing. this timing has no noticeable effect on performance of the circuit, but can have an impact on the nature of rf spectral emissions from the matrix panel. the setting of this function can be from 1s to 10s, loosely corresponding to fundamental emission frequencies of from 1mhz to 100khz respectively. longer spacings require more time to execute and can limit the operational settings of burst length and/or burst spacing (section 5.7). the intra-burst qt spacing has no effect on sensitivity or water film suppression and is not particularly important to the sensing function other than described above. 3.8 burst spacing see also command ^g, page 22 the interval of time from the start of one burst to the start of the next is known as the burst spacing . this is an alterable parameter which affects all keys. shorter spacings result in faster response time, but due to increasing timing restrictions at shorter spacings burst lengths or the conversion resolution may be restricted, limiting the amount of gain that can be obtained; see sections 3.6 and 5.7. conversely longer spacings permit higher burst lengths but slow down response time. three settings of burst spacing are possible : 500s, 1ms, and 2ms. 3.9 sample capacitors charge sampler capacitors cs should be either ceramic npo, x7r 5%, or pps film for stability reasons. the values of capacitance should not be altered from that shown in the schematic of figure 3-2 without good reason. changes in cs have only a limited effect on signal gain. 3.10 water film suppression water films on the user surface can cause problems with false detection under certain conditions. water films on their own will not normally cause false detections. the most common problem occurs when surface water bridges over 2 or more keys, and a user touches one of the keys and the water film causing an adjacent key to also trigger. essentially, the water film transports the touch contact to adjacent keys. the circuit suppresses water coupling by having a short dwell time, equal to one oscillator period or 83ns. a short dwell time reduces the amount of charge collected via resistive water films, i.e. it suppresses charge from areas adjacent to the scanned key. this effect has nothing to do with the frequency of the burst itself. very short dwell times can cause excess suppression of human touch as well. if series resistors are used in line with the x and y matrix lines for noise and esd suppression (section 3.18), a short dwell time can seriously affect signal gain. mechanical measures can also be used to suppress key cross-coupling, for example one can use raised plastic barriers between keys, or placing keys in shallow wells to lengthen the electrical path from key to key. 3.11 reset input the rst pin can be used to reset the device to simulate a power down cycle, in order to bring the part up into a known state should communications with the part be lost. the pin is active low, and a low pulse lasting at least 10s must be applied to this pin to cause a reset. to provide for proper operation during power transitions the devices have an internal brown-out detector set to 4 volts. a reset command, r , is also provided which generates an equivalent hardware reset (page 25). 3.12 oscillator the oscillator can use either a quartz crystal or a ceramic resonator. in either case, the xti and xto must both be loaded with 22pf capacitors to ground. 3-terminal resonators having onboard ceramic capacitors are commonly available and are recommended. an external ttl-compatible frequency source can also be connected to xti; xto should be left unconnected. the frequency of oscillation should be 12mhz + /-2%. 3.13 startup / calibration times the qt60161b requires initialization times as follows : 1. from very first powerup to ability to communicate : 2,000ms (one time event to initialize all of eeprom) 2. normal cold start to ability to communicate : 70ms (normal initialization from any reset) 3. calibration time per key vs. burst spacings : spacing = 500s : 100ms spacing = 1ms : 150ms spacing = 2ms : 300ms to the above, add 2,000ms or 70ms from (1) or (2) for the total elapsed time from reset to ability to report key detections. keys that cannot calibrate for some reason require 5 calibration cycles before they report as errors. however, the device can report back during this interval that the key(s) affected are still in calibration via status function bits. 3.14 sleep_wake / noise sync pin (ws) the sleep _ wake and noise sync features use input pin ws. the sleep and sync features can be used simultaneously; the part can be put into sleep mode, but awakened by a noise sync signal which is gated in at the time desired. sleep mode: see also command ? z ? , page 25. the device can be put into an ultra low-power sleep mode using the z command. when this command is received, the ws pin must be placed immediately thereafter into a logic-high state. the part will complete an ongoing burst before entering sleep. the part can be awakened by a low transition on the ws pin lasting at least 5s. one convenient way to wake the part is to connect ws to mosi, and have the host send a null ?quantum research group ltd. l q 9 www.qprox.com qt60161b / r1.03
command to the device. the part will wake and the null command will not be processed. the mosi line in turn requires a pullup resistor to prevent the line from floating low and causing an unintentional wake from sleep. during sleep the oscillator is shut down, and the part hibernates with microamp levels of current drain. when the part wakes, the part resumes normal functionality from the point where it left off. it will not recalibrate keys or engage in other unwarranted behavior. j ust before going to sleep the part will respond with a response of ' z '. in slave-only spi mode (see section 4.3), the ss line must be floated high by the host as soon as it receives this response; if ss does not float high, sleep will fail and the device will instead completely reset after about 2 seconds. upon waking the part will issue another ' z ' byte back to the host. noise sync: see also command ^w, page 26 . external fields can cause interference leading to false detections or sensitivity shifts. the strongest external fields usually come from ac power. rf noise sources are heavily suppressed by the low impedance nature of the qt circuitry itself. external noise only becomes a problem if the noise is uncorrelated with signal sampling; uncorrelated noise can cause aliasing and beat effects in the key signals. to suppress this problem the devices feature a noise sync input which allows bursts to synchronize to the noise source. this same input can also be used to wake the part from a low-power sleep state. the device s bursts can be synchronized to an external source of repetitive electrical signal, such as 50hz or 60hz, or possibly a video display vertical sync line, using the sleep _ wake / noise sync line. the noise sync operating mode is set by command ^w. this feature allows dominant external noise signals to be heavily suppressed, since the system and the noise become synchronized and no longer beat or alias with respect to each other. the sync occurs only at the burst for key 0 (x0y0); the device waits for the sync signal for up to 100ms after the end of a preceding full matrix scan (after key # 15), then when a negative sync edge is received, the matrix is scanned in its entirety again. the sync signal drive should be a buffered logic signal, or perhaps a diode-clamped signal, but never a raw ac signal from the mains. since noise sync is highly effective yet simple and inexpensive to implement, it is strongly advised to take advantage of it anywhere there is a possibility of encountering electric fields. quantum s qmbtn software can show signal noise caused by nearby ac electric fields and will hence assist in determining the need to make use of this feature. if the sync feature is enabled but no sync signal exists, the sensor will continue to operate but with a delay of 100ms from the end of one scan to the start of the next, and hence will have a slow response time. 3.15 led / alert output pin 40 is designed to drive a low-current led, 5ma maximum, in an active-low configuration. higher currents can cause significant level shifts on the die and are not advised. the led will glow brightly (i.e. pin 40 will be solid low) during calibration of one or more keys, for example at startup. when a key is detected, the led will pulse low for the duration of ?quantum research group ltd. l q 10 www.qprox.com qt60161b / r1.03 figure 3-2 recommended circuit diagram
the burst during which the key is being sensed, i.e. with a very low duty cycle. each additional key being detected will also create a low pulse for that key s burst. during all other times, the led pin will be off (high). this pin can be used to alert the host that there is key activity, in order to further limit the amount of communication between the device and the host. the led / alert line should ideally be connected to an interrupt pin on the host that can detect a negative edge, following which the host can proceed to poll the device for keys. this line also pulls low if there is a key error of any kind. note that in sleep mode if the led was on prior to sleep, it will remain on during sleep. 3.16 oscilloscope sync see also command ^r, page 26 the so pin can output an oscilloscope sync signal which is a positive pulse that brackets the burst of a selected key. this feature is controlled by the ^r command. more than one burst can output a sync pulse, for example if the scope of the command when set is a row or column, or is all keys. the ^r command is volatile and does not survive a reset or power down. this feature is invaluable for diagnostics; without it, observing signals clearly on an oscilloscope for a particular burst is nearly impossible. this function is supported in qmbtn pc software via a checkbox. 3.17 power supply & pcb layout vdd should be 5.0 volts + /- 5%. this can be provided by a common 78l05 3-terminal regulator. ldo type regulators are often fine but can suffer from poor transient load response which may cause erratic signal behavior. if the power supply is shared with another electronic system, care should be taken to assure that the supply is free of low-level spikes, sags, and surges which can adversely affect the circuit. the devices can track slow changes in vcc depending on the settings of drift compensation, but signals can be adversely affected by rapid voltage steps and impulse noise on the supply rail. supply bypass capacitors of 0.1uf to a ground plane should be used near every supply pin of every active component in the circuit. pcb layout: the pcb layout should incorporate a ground plane under the entire circuit; this is easily possible with a 2-layer design. the ground plane should be broken up as little as possible. internal nodes of the circuit can be quite sensitive to external noise and the circuit should be kept away from stray magnetic and electric fields, for example those emanating from mains power components such as transformers and power capacitors. if proximity to such components is unavoidable, an electrostatic shield may be required. the use of the sync feature (section 3.14) can be invaluable in reducing these types of noise sources, but only up to a point. 3.18 esd / noise considerations in general the qt60161b will be well protected from static discharge during use by the overlying panel. however, even with a dielectric panel transients currents can still flow into scan lines via induction or in extreme cases, dielectric breakdown. porous or cracked materials may allow a spark to tunnel through the panel. in all cases, testing is required to reveal any potential problems. the ic has diode protected pins which can absorb and protect the device from most induced discharges, up to 5ma. the x lines are not usually at risk during operation, since they are low-resistance output drives. diode clamps can be used on the x and y matrix lines if desired. the diodes should be high speed / high current types such as bav99 dual diodes, connected from vdd to vss with the diode junction connected to the matrix pin. diode arrays can also be used. capacitors placed on the x and y matrix lines can also help to a limited degree by absorbing esd transients and lowering induced voltages. values up to 100pf on the x lines and 22pf on the y lines can be used. the circuit can be further protected by inserting series resistors into the x and/or y lines to limit peak transient current. rc networks as shown in figures 4-6 and 4-7 can provide enhanced protection against esd while also limiting the effects of external emi should this be a problem. external field interference can occur in some cases; these problems are highly dependent on the interfering frequency and the manner of coupling into the circuit. pcb layout (section 3.17) and external wiring should be carefully designed to reduce the probability of these effects occurring. spi / uart data noise: in some applications it is necessary to have the host mcu at a distance from the sensor, perhaps with the interface coupled via ribbon cable. the spi link is particularly vulnerable to noise injection on these lines; corrupted or false commands can be induced from transients on the power supply or ground wiring. bypass capacitors and series resistors can be used to prevent these effects as shown in figures 4-6 and 4-7. 4 communications interfaces the qt60161b uses parallel, uart, and spi interfaces to communicate with a host mcu. the serial interfaces use a protocol described in section 5. only one interface can be used at a time; the interface type is selected by resistor-coupled jumpers connected to pins x0opa (pin 13) and x0opb (pin 14) shown in table 4-1. see also figure 3-2. further specific information on each interface type is contained in the following sections : spi slave-only mode : section 4.3 spi master-slave mode : section 4.4 uart interface : section 4.5 parallel interface : section 4.7 4.1 serial protocol overview the spi and uart interface protocols are based entirely on polled data transmission, that is, the part will not send data to the host of its own volition but will do so only in response to specific commands from a host. ?quantum research group ltd. l q 11 www.qprox.com qt60161b / r1.03
run-time data responses, such as key detection or error information, requires simple single-byte functions to evoke a response from the part. setup mode interactions mostly use 2-byte functions from the host to cause the part to alter its behavior; these functions also cause writes to the internal eeprom. the concept of 'scope' is used to allow functions to operate on individual keys or groupings of keys. the scope of subsequent functions can be altered by short initial scope instructions. see section 5 for protocol details. 4.2 spi port specifications the part has an spi synchronous serial interface with the following specifications at 12mhz oscillator frequency : max clock rate, fck 3mhz data length 8 bits host command space, tcm m 50s response delay to host, tdr1 table 4-1, also, sec. 6 drdy delay from response, tdr2 1s to 1ms multi-byte return spacing, tdr3 10s to 2ms the host can clock the spi with the part in slave mode at any rate up to and including the maximum clock rate fck. the maximum clock rate of the part in master mode is determined by setup ^q (page 25). the part can operate in either master-slave mode or slave-only mode, and is thus compatible with virtually all spi-capable microcontrollers. the spi interface should not be used over long distances due to problems with signal ringing and introduced noise etc. unless suitably buffered or filtered with rc networks as shown in figures 4-6 and 4-7. slower data rates with longer rc timeconstants will provide enhanced resistance to noise and ringing problems. 4.3 spi slave-only mode refer to figures 4-1, 4-3 and 4-2. in slave-only mode the host must always be in master mode, as it controls all spi activity including the clocking of the interface in both directions. unlike hardware spi slaves, the qt60161b needs processing time to respond to functions. drdy is used to let the host know when data is ready for collection; it indicates to the host when data is ready in response to a command so that the host can clock over the data. this mode requires 5 signals to operate : mosi - master out / slave in data pin; used as an input for data from the host at all times. this pin should be connected to the mosi pin of the host device. miso - master in / slave out data pin; used as an output for data to the host at all times. this pin should be connected to the miso pin of the host device. sck - spi clock - input only clock pin from host. the host must shift out data on the falling edge of sck; the qt60161b clocks data in on the rising edge of sck. important note: sck must idle low just before and after ss transitions either up or down, or the transmission will fail; between bytes sck should idle low. ss - slave select - input only; this pin acts as a framing signal to the sensor from the host. this line must go low just before and during reception of data from the host. it must not go high again until the sck line has returned low; during data or echo response it must not go high until after the host has sensed that drdy has gone high from the device. this pin must idle high. the ss pin has an internal pullup resistor inside. drdy - data ready - active-low - indicates to the host that the part is ready to send data back subsequent to a command from the host. this pin idles high. the drdy pin has an internal pullup resistor inside. internal pullup resistors note: the internal pullup resistors can range from 35k to 120k ohms. if rc filtering is used on the spi lines per figure 4-6, this resistance may not be low enough to ensure adequate signal risetime and may need to be augmented with external 10k pullups. the host must wait until drdy goes low before an spi transfer to retrieve data. for multi-byte responses, the host must observe drdy' to see when it goes high again after each data byte, then low again, before executing another transfer to get the next data byte. the host should send null bytes (0x00) to retrieve data. if the drdy line does not go low after a command, the command was not properly received or it was inappropriate. the delay to drdy low depends on the command and how many bytes of data are being stored into eeprom; table 4-1 shows the maximum delays encountered in most cases. absolute worst case delays are found in section 6-5; these timings occur only rarely, for example if the device happens to be busy with adjacent key suppression calculations, which occurs only at the moment when a key is first detected. a typical slave-only function sequence is as follows : 1) the host pulls ss low, then transfers a command to the sensor. the host then releases ss to float high. drdy is unaffected in this step. 2) for 2-byte functions, (1) is repeated with a m 50us delay. 3) when the sensor has the command echo or requested data ready to send back to the host, it loads it into its spi register and pulls drdy low. 4) the host detects that the sensor has pulled drdy low and in turn the host pulls ss low. 5) the host obtains the byte from the sensor by transmitting a dummy byte (0x00) to the sensor. 6) the sensor releases drdy to float high. 7) after the host detects that drdy' has floated high the host must allow ss to also float high. 8) for multi-byte responses, steps (3) through (7) are repeated until the return data is completely sent. note that the host must release the ss line in step (7) even between multiple byte responses because the qt60161b waits for the ss line to return high before signalling that the next byte is ready for collection. note also that the host should check the drdy line and wait for it to go high before transmitting another byte. until the drdy line is released the sensor is still processing a data return, even if the complete response data has been fully transferred; the sensor may still be busy when the host finishes the byte transfer and may not be able to digest a new command immediately. ?quantum research group ltd. l q 12 www.qprox.com qt60161b / r1.03
see section 3.15, page 10, for a description of the alert pin which can be used to reduce communication traffic. 4.4 spi master-slave mode refer to figures 4-1, 4-2, and 4-4. in master-slave mode the host and the sensor take turns being master, with the host always leading off in master mode during an exchange. the current master always controls all 3 signal lines. the sensor takes a variable amount of time to respond to the host, depending on the nature of the function and its current and pending tasks. the host, like the sensor, must idle in slave mode when not sending a command. master/slave requires 3 signals to operate : mosi - master out / slave in data pin - bidirectional - an input pin while the host is transmitting data; an output when the sensor is transmitting data. the mosi of the host and slave should be tied together. the miso lines are not used on either part and should be left open. sck - spi clock - bidirectional - an input pin when receiving data; an output pin when sending. the host must shift out data on the falling edge of sck; the qt60161b clocks data in on the rising edge of sck. important note: sck from the host must be low before asserting ss low or high at either end of a byte or the transmission will fail. sck should idle low; if in doubt, a 10k pulldown resistor should be used. when the sensor returns data it becomes the master; data is shifted out by it on the falling edge of sck and should be clocked in by the host on the rising edge. ss - slave select - bidirectional framing control. when the sensor is in slave mode, this pin accepts the ss control signal from the host. in either data direction, ss' must go low before and any during data transfer; it should not go high again until sck has returned low at the end of a byte. in master mode the sensor asserts control over this line, to make the host a slave and to frame the data. this line must idle high; the part includes an internal pullup resistor and should be floated during idle times. internal pullup resistor note: the internal pullup resistor on ss can range from 35k to 120k ohms. if rc filtering is used on the spi lines per figure 4-7, this pullup resistance may not be low enough to ensure adequate signal risetime and may need to be augmented with external 10k pullups. a command may consist of one or two bytes with a m 50us delay between command bytes. at the end of a full command, the master must go into slave mode to await a response from the sensor. the sensor may take some time to process the host command and respond. when it does so, it asserts ss low and begins clocking its data. for multi-byte responses, the bytes will be sent at intervals which may be somewhat irregular depending on the request and the processing load of the sensor. the host must be prepared to accept the sensor data as it comes or there can be a data overrun in the host. if the data returns too fast for the host to accept it, the spi clock rate should be lowered. a typical master-slave function sequence is as follows : 1) host enters master mode. the sensor is already in slave mode. 2) the host pulls ss low, then transfers one byte of command to the sensor via mosi, then releases ss to float high again. 3) for 2-byte functions, (2) is repeated with m 50us spacings between bytes. 4) the host immediately places its spi port into slave mode, floating sck and mosi ; ss stays floating. 5) when the sensor has a command echo or data to send back, it puts its spi register in master mode, taking control over mosi and sck. ss' remains floating. 6) the sensor pulls ss low, then clocks out its response byte to the host, then floats ss high again. 7) the sensor repeats (6) as necessary for multiple byte responses. 8) the sensor returns to slave mode. after the transmission sequence, the spi lines float high or are left to float in an indeterminate state (mosi) until the next transmission sequence is initiated by the host. the host should wait for > 1ms after a sequence before initiating another transmission sequence. see section 3.15, page 10, for a description of the alert pin which can be used to reduce communication traffic. ?quantum research group ltd. l q 13 www.qprox.com qt60161b / r1.03 figure 4-2 spi connections slave-only master-slave mosi mosi miso miso sck sck drdy p_out p_in ss ss host m c u q t60 x x 5 vdd ss mosi mosi sck sck drdy ss host mcu qt60 x x 5 miso miso figure 4-1 communications option jumpers x0 x1 v cc opt a opt b to m a t ri x 10k 10k l h h l 13 14 parallel high high spi, master/slave low high uart high low spi, slave only low low interface type x0opb (pin 14) x0opa (pin 13)
4.5 uart interface refer to figures 4-1 and 4-5. uart communications requires only 2 wires, tx and rx to communicate with a host device. all communications must be initiated by the host. the baud rate is determined by setup ^q (page 25); the maximum baud rate with a 12mhz oscillator is 57.6k. uart communications uses the following settings : ?quantum research group ltd. l q 14 www.qprox.com qt60161b / r1.03 table 4-1 typical tdr1 response delays (100s sample ramp) 350s 350s 350s all other commands 350s 350s 350s get keys pushed (k) 450s 450s 450s get key errors (e) 500s 500s 500s calibrate command (all keys) 65ms 65ms 65ms lock reference level (l) 65ms 65ms 65ms setup - put (affect 16 keys) 20ms 20ms 20ms setup - put (affect 8 keys) 10ms 10ms 10ms setup - put (affect 1 key) 2ms 1ms 500s f un c tion ty pe b urst spa c in g figure 4-5 uart timing rx {from host} optional byte 2 from host to sensor command byte 1 from host to sensor t dr1 response byte or echo from sensor to host nth byte from sensor {n = command dependent} t cm 7 6 5 4 3 2 1 0 s tx {from sensor} 7 6 5 4 3 2 1 0 s 7 6 5 4 3 2 1 0 s 7 6 5 4 3 2 1 0 s t dr3 figure 4-4 spi master/slave mode timing sck mosi optional byte 2 from host to sensor command byte 1 from host to sensor ss t dr1 response byte or echo from sensor to host nth byte from sensor {n = command dependent} ss, sck, mosi originate from host ss, sck, mosi originate from sensor 7 6543210 7 6543210 7 6543210 7 6543210 floating t cm t dr3 figure 4-3 spi slave-only mode timing sck {from host} mosi {from host} miso {from sensor} invalid data optional byte 2 host command byte 1 null dummy data null dummy data invalid data response data or echo nth response data {n = command dependent} drdy {from sensor} ss {from host} 7 6543210 7 6543210 7 6543210 7 6543210 7 6543210 7 6543210 t dr1 t cm t dr2 t dr3
baud rate 9,600 - 57,600 data length 8 bits parity none stop bits 1 host command space, tcm m 50s response delay to host, tdr1 table 4-1, also, sec. 6 multi-byte return spacing, tdr3 10s to 2ms the actual baud rate is determined by setup ^q (page 25). a uart command may consist of one or two bytes with a m 50us delay between command bytes. at the end of a full command, the host must await a response from the sensor. the sensor may take some time to process the host command and respond. when it does so, it sends back its data. for multi-byte responses, the bytes will be sent at intervals which may be somewhat irregular depending on the request and the processing load of the sensor. the host must be prepared to accept the sensor data as it comes or there can be a data overrun in the host. if the data returns too quickly for the host to accept it, the baud rate should be lowered . a typical uart communication sequence is as follows : 1) host sends a byte to the sensor. 2) for 2-byte functions, a m 50us delay is inserted by the host and then the second byte is sent. 3) if the sensor has a command echo or data to send back, it does so. the delay from step 2 to step 3 is shown in table 4-1. the delay between successive response bytes (if they occur) is parameter tdr3 noted above. 4) the sensor repeats (3) as necessary for multiple byte responses. 5) the sensor waits for the next command. the host should wait for > 1ms after a sequence before initiating another transmission sequence to be sure that the sensor has completed any residual activities from the prior command. commands that are sent to the host prematurely will be ignored. 4.6 sensor echo and data response the devices respond to each and every valid command from the host with at least one return byte. in the case of functions that do not send data back to the host, the part returns the command itself as an echo, but only after the function has been processed to completion; this also holds for 2-byte functions where the second byte is an operand : in these cases the return byte is an echo of the command, not the operand. one important exception to this is the recalibration command b which returns an acknowledgment immediately rather than prior to the actual recalibration. commands that return data do not send back a command echo. if desired, the command byte can be verified via the 'l' (lowercase l) function; see page 25. the host should not transmit a new command until the last command has been processed and responded to completion, plus 1ms. commands that are not recognized are ignored, and the host should monitor for timeouts to detect these conditions. if this occurs a new command should not be sent until the specified timeout condition has expired. the maximum timings shown in table 4-1 and section 6-5 are guaranteed provided that the part is operating within its burst timing limitations described in section 5.7. if the burst timing is in violation, the response time to a command may take considerably longer. 4.7 parallel scan port the parallel port can be used to directly replace an electro- mechanical or membrane keyboard. the port is electrically equivalent to a 4x4 switch matrix with the exception that the response to a host scan requires up to 100s. the xs inputs (pins 19..22) are active high; only one xs line should ever be driven high at a time (except for error scan, noted below); the ?quantum research group ltd. l q 15 www.qprox.com qt60161b / r1.03 figure 4-6 filtering; spi slave-only connections mosi miso sck drdy ss qt60161 circuit ra 220 47pf ra ra ra ra reset 1k host mcu 100 22pf yn xn x drives (1 of 4 shown) y lines (1 of 4 shown) 10k + 5 ca ca ca ca ca 1nf 10k + 5 sck miso mosi (ms not shown) p_in p_out1 p_out2 figure 4-7 filtering; spi master-slave connections mosi miso sck drdy ss qt60161 circuit 220 47pf ra ra ra reset 1k host mcu 100 22pf yn xn x drives (1 of 4 shown) y lines (1 of 4 shown) ca ca ca ca 1nf 10k +5 mosi ca ca ss sck miso (ms not shown) p_out 470pf 2,200 93.75khz 270pf 1,000 187.5khz 120pf 1,000 750khz 47pf 680 3mhz ca ra spi clock rate recommended values of ra & ca for figures 4-6 and 4-7
output response is found on the ys lines (pins 23..26), and these are also active high. the bit pattern found on the ys lines indicates any keys that are touched; like a real matrix, the device can set multiple bits on the ys lines. the host should scan to individual lines xs0..xs3. xs0 maps to matrix drive line x0 (pin 13). the response on ys0 maps to matrix line y0. thus, the scan port logic exactly mimics the wiring and scanning of the matrix keys. the parallel scan port operates on a continuous basis, but is slower to react when either serial port is in operation. if either serial port is operational, the scan port updates with every acquisition burst, i.e. 16 times during a complete scan of the matrix. for a full-time higher speed scan port response, it should be enabled as the sole interface via the option jumper settings shown in figure 4-1. the port itself is found on pins 19 through 26 (figure 3-2). in this dedicated mode, the scan port outputs within 100s of receiving a scan input from the host. error scan: the host can extract error information from the scan port by setting all xs lines to logical '1' simultaneously. the part then returns a high level on any ys lines corresponding to y matrix lines having key errors. thus a single ys bit, if high, could indicate errors on any or all of 4 keys. errors are reported for the following conditions : a. key(s) are currently recalibrating b. key(s) tried to calibrate 5 times and failed each time c. key(s) signal references are under- or over- limit it is not possible to determine the cause of the error or specific key(s) in error via the parallel scan port. 4.8 eeprom corruption the device stores its setup data in an internal eeprom which can be readily altered via put mode commands. sometimes noise on vdd, the spi lines or reset pin can cause eeprom corruption which can be difficult or inconvenient to correct. the device should always be left in get mode to prevent spurious commands from corrupting the eeprom. the get command should ideally be repeated every second or so to ensure that if noise on the spi lines causes a false put mode command that it does not last long. preferably, the l command (lowercase l ) should be used to verify that the put command has succeeded. f las h b a ck up: the part backs up the entire eeprom array into onboard flash rom after one or more setup write commands have been issued and the part is then reset. during normal operation the part constantly compares the flash area with the eeprom array to ensure the two sections match. if an eeprom error is detected, the device sets an error flag (bit 4) in the general device status byte (command 7 , page 19) which can be read by the host device. the led output also becomes active. if the bit 4 error flag is set, the host should immediately induce a device reset. bit 4 is also set if an intentional write has been made to eeprom, but not yet copied into flash via the reset process. it is perfectly acceptable to continue altering any number of setup parameters prior to doing the reset, ignoring this bit. during power up or after a reset, the device compares the flash area with eeprom, and if there is a discrepancy the eeprom is refreshed from flash, unless an intentional write was detected in which case the flash is updated from the eeprom. as intentional writes in put mode should only occur during manufacture, it is normally safe to assume that eeprom changes during normal run mode are errors. the host can also periodically test the checksum of the eeprom as a backup mechanism to the bit 4 error flag. the uppercase l command, lock reference levels, also writes data to eeprom, and this data also has the potential to become corrupted. this data is also backed up in flash so that it can be recovered, and an error in this data will also set bit 4 and also alter the checksum. also, the l command only operates if the device is in put mode as a further protection. flash memory has a limit of 1,000 write cycles, so copy-to-flash should not be used often. ?quantum research group ltd. l q 16 www.qprox.com qt60161b / r1.03
5 commands & functions the command structure is designed to minimize control and data traffic. all repetitive data and status commands from the host are single-byte, and most commands result in single- byte device responses. behavioral setup commands involve multiple bytes but these are infrequently used. special 'scope' commands exist to restrict subsequent commands to a specific key or range of keys. this control structure permits most matrix keys, which are usually identical in shape and size, to be programmed 'in bulk' using a 'global' scope command, followed by a scope restriction to specific key(s), followed by more key programming, to prevent the need for tedious key-by-key programming across an entire matrix. there are four types of commands : d ire c tion - determine whether subsequent commands are used to get data from or put data to the part; s c ope - restrict the range of effect of subsequent commands to a specific set of keys; status - cause the part to respond with key information, such as detections, signals, error codes, and the like; setup - modify functionality such as burst length, threshold levels, drift compensation characteristics, etc. super v isor y - special functions such as diagnostics, calibration, etc. which affect the part as a whole. all command types can be intermixed. even during normal device operation it is possible to use setup and supervisory functions to alter key behavior on the fly. there is no special 'setup mode'. get/put, scope, and many supervisory functions are volatile and do not persist after a power down or reset cycle. some supervisory commands require that the part be reset in order for the new settings to take effect. note that the setup functions write to eeprom and require extra time for a response back to the host. also note that as with all eeprom memories there is a recommended lifetime limit to the number of writes; this limit is 100,000 cycles. command functions are summarized in section 5-6. it is highly advised to test the device checksum (command ?6?, page 18) or individual settings or the general device status (?7?) once setups have been programmed into the part, each time the part is powered up and periodically while running. the part backs up all eeprom locations into flash, from which data is restored automatically following a reset if eeprom corruption is detected. the part should also be reset after any put command(s) in order to force the copy of eeprom data into flash. see section 4.8. 5.1 put / get direction commands setup commands can be used to either send control information to the part for programming into its internal eeprom, or to extract the current setting of this information. the same setup function can do either. to accomplish this the device relies on direction control via the get and put commands. in get mode, a setup command will return information. in put mode, the behavior of the device is altered, and often a second operand byte must be sent. the powerup or reset default mode is get. the current get/put mode persists until countermanded by a different get/put command or until the device is reset or powered off. it is advisable to use put mode only when actually writing setups to the device, which will happen infrequently; the part should normally be left in get mode. get mode acts as a lock to prevent accidental changes to the internal eeprom. multiple direction commands of the same type (g, g, g, g ...) are harmless and can be used to insure that the part does not accidentally enter put mode for a prolonged period, for example due to noise glitches on the spi lines. the 'g' command can be repeated every few seconds. g 0 x 67 - g et c ommand n/a n/a n/a n/a get 0x67 n/a 1 n/a put return s 2nd b y te ran ge b y tes / cm d scop e lowercase 'g'. the 'g' command causes the device to treat all subsequent setup commands as 'gets'; after, when a setup command is received from the host the part will respond by sending back the current status of that setup parameter. the 'g' command is always single-byte and echoes back itself. p 0 x 70 - p ut c ommand n/a n/a n/a n/a get 0x70 n/a 1 n/a put returns 2nd byte range bytes / cmd scope lower case 'p'. the 'p' command causes the device to treat all subsequent setup commands as 'puts'; after, when a 2-byte setup command is received from the host the part will respond by programming in the desired parameter for the key(s) which are affected. the 'p' command is always single-byte and echoes back itself. ?quantum research group ltd. l q 17 www.qprox.com qt60161b / r1.03
5.2 scope commands the host should always set the scope parameter when initializing the part during normal operation as well as during setup. scope commands are persistent and apply to all subsequent functions that are affected by scope, until a different scope command is issued. on powerup or after reset the device defaults to scope = 'all keys'. many functions only address one key regardless of the current scope; in these cases the key being addressed is always the key last set by the s or x and y commands. if the s command was last set to key 9, then even though the s command was issued afterwards the one-key scope will remain key 9 . similarly if x was set to 2 and y to 3, then the one-key scope will remain key x=2 / y=3 (key # 14). this rule operates for either put or get commands. ke y num b erin g c on v ention: the numbering of keys goes by row then column. for example, the key in row x=3, column y=1 (x3y1) is key 7. the formula for conversion of an x-y location to a key number is : key number = x _ row + (y _ column x 4) row and column numbers are per fig. 1-5. keys are acquired in this same burst sequence, i.e. x0y0, x1y0, x2y0 etc. s 0 x 73 - s pecific k ey s cope n/a n/a n/a n/a get 0x73 0x00..0x0f 2 n/a put return s 2nd b y te ran ge b y tes / cm d scop e lowercase 's'. targets a specific individual key for all further functions that are affected by scope. the second byte must contain a binary key number from 0..15. s 0 x 53 - a ll k eys s cope n/a n/a n/a n/a get 0x53 n/a 1 n/a put return s 2nd b y te ran ge b y tes / cm d scop e uppercase 's'. addresses all keys in the matrix for all further functions that can target a group of keys. x 0 x 78 - r ow k eys s cope n/a n/a n/a n/a get 0x78 0x00..0x03 2 n/a put returns 2nd byte range bytes / cmd scope lowercase 'x'. targets keys in a specific row for functions that can address key groups. the second byte must contain a row number from 0..3. y 0 x 79 - c olumn k eys s cope n/a n/a n/a n/a get 0x79 0x00..0x03 2 n/a put return s 2nd b y te ran ge b y tes / cm d scop e lowercase 'y'. targets keys in a specific column for functions that can address key groups. the second byte is a binary column number from 0..3. 5.3 status commands status commands cause the sensor to report back information related to keys and their signals. it is not necessary to set the part to get mode with these commands, although it is advised to leave the part in get mode as a normal precaution (see section 5.1) 0 0 x 30 - s ignal for s ingle k ey 0..0xffff 2 1 1 get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e numeric '0'. returns the signal level in 16-bit unsigned binary for one key whose location is determined by scope. the least significant byte is returned first. note that the signal direction is inverted : decreasing values correspond to more touch due to the physics of key detection described in section 1.1. 1 0 x 31 - d elta s ignal for s ingle k ey 0x00..0xff 1 1 1 get n/a n/a n/a n/a put returns # bytes rtnd bytes / cmd scope numeric '1'. returns the value { reference - signal } in unsigned 8-bit binary for one key whose location is determined by scope. if signal > reference, the result is truncated to zero. the return value is also limited to 255 (0xff). increasing amounts of this value correspond to increasing amounts of touch as the sign of signal is inverted (see 0x30 above). 2 0 x 32 - r eference v alue 0..0xffff 2 1 1 get n/a n/a n/a n/a put returns # bytes rtnd bytes / cmd scope numeric '2'. returns the reference value in unsigned 16-bit binary for one key whose location is determined by scope. the least significant byte is returned first. 5 0 x 35 - d etection i ntegrator c ounts 0x00..0xff 1 1 1 get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e numeric '5'. returns the detection integrator counter value for one key whose location is determined by scope. this function is useful primarily for circuit diagnostics. 6 0 x 36 - e eprom c hecksum 0 x 00..0xff 1 1 n/a get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e numeric '6'. returns the entire eeprom checksum. this function is useful primarily for diagnostics and should periodically be used to check for valid eeprom contents. the checksum should be computed when the entire device's settings, including the locked reference levels ('l' command) are known. the host can then periodically test the checksum to validate eeprom integrity. if needed, the eeprom can then ?quantum research group ltd. l q 18 www.qprox.com qt60161b / r1.03
be reprogrammed by the host or the device can be reset to allow the eeprom to be updated from flash memory (see section 4.8). the checksum is a simple 8-bit carry fold-back type. changes to multiple setups can generate identical checksums. changes to one location only will always produce a different checksum. an identical change to 2, 4, 8, or all 16 keys is more prone to generating an identical checksum. a unique checksum can be obtained again by altering any setup for another key (i.e. an unused key) to be different. after any setups change, the checksum will not be valid until after the device has been reset. note that the status byte returned by the 7 command contains a bit that is set if there is an error in eeprom data; this feature operates independently of the checksum command. there is no put version of the command. 7 0 x 37 - g eneral d evice s tatus 0x00..0x1f 1 1 n/a get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e section 2.11, p. 7 numeric '7'. returns the part's general status byte which is a 4-bit pattern as follows : bit 0 : 1= one or more keys are in detection bit 1 : 1= one or more keys are recalibrating bit 2 : 1= one or more keys are reporting errors bit 3 : 1= sync fail; the part is not synchronized to an external source (if in that mode; see section 3.14). bit 4 : 1 = eeprom / flash contents discrepancy higher bits report as 0's and are not used. this command can be used as a general 1-byte status response; if one or more bits are set, the host can take further relevant action to narrow down the specific issue, such as which key is being touched or in error, via other commands. < sp > 0 x 20 - s ignal l evels for g roup 0..0xffff 8 or 32 1 4, 16 get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e space character. same function as 0x30 above except returns a group response for 4 keys (if scope = row or column) or 16 keys (if scope = 'all keys'). if no group scope has been selected, returns data for all keys (32 bytes). two bytes are returned for each key; the least significant byte is always returned first. ! 0 x 21 - d elta s ignals for g roup 0x00..0xff 4 or 16 1 4, 16 get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e exclamation character. same function as 0x31 above except returns a group response for 4 or 16 keys depending on scope. if no group scope has been selected, returns data for all 16 keys (16 bytes). the values returned are limited to the range 0..255. " 0 x 22 - r eference l evels for g roup 0..0xffff 8 or 32 1 4, 16 get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e double quote character. same function as 0x32 above except returns a group response for 4 or 16 keys depending on scope. if no group scope has been selected, returns data for all 16 keys (32 bytes). % 0 x 25 - d etect i ntegrator c ounts for g roup 0 x 00..0xff 4 or 16 1 4, 16 get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e percent character. same function as 0x35 above except returns a group response of 4 bytes (scope = row or column) or 16 bytes (scope = 'all keys'). if no group scope has been selected, returns data for all 16 keys. e 0 x 65 - e rror c ode for s elected k ey 0 x 00..0x0f 1 1 1 get n/a n/a n/a n/a put returns # bytes rtnd bytes / cmd scope section 2.11, p. 7 lowercase 'e'. returns the error byte for a selected key defined by the 's' command. a 4-bit pattern is returned : f r h l u u u u b0 b1 b2 b3 b4 b5 b6 b7 f : 1= failed last full recalibration attempt r : 1= key is in process of full recalibration h : 1= key reference is high (above normal bounds) l : 1= key reference is low (below normal bounds) u : undefined refer also to section 2.10. f, b it 0 is set if it failed to calibrate properly during a forced recalibration. the sensor will automatically make 5 sequential attempts at recalibration before setting this flag. r, b it 1 is set if the key is in the process of a full recalibration. when bit 1 is set, bits 2 and 3 are cleared. h, b it 2 when set indicates that the key's reference level has exceeded the upper boundary described in section 2.8 and as defined by command ^n (page 23). l, b it 3 when set indicates that the key's reference level falls below the lower boundary described in section 2.8 and as defined by command ^o (page 23). if either h or l are set, it means that the key is probably defective. ?quantum research group ltd. l q 19 www.qprox.com qt60161b / r1.03
e 0 x 45 - e rror c odes for g roup 0x00..0xff 1 or 4 1 1, 4, 16 get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e section 2.11, p. 7 uppercase 'e'. returns general error codes for a range of keys defined by scope. returns either 1 or 4 bytes depending on whether a single key, row, column, or entire matrix are selected. the bitfields for single key scope are the same as for 'e' above. the bitfields for a single row (x) are : y 0 y1 y2 y 3 - - - - b0 b1 b2 b3 b 4 b 5 b6 b7 the bitfields for a single column (y) are : x0 x1 x2 x3 - - - - b0 b1 b2 b3 b4 b5 b6 b7 the bitfields for a global response are : x0y3 12 x1y3 13 x2y3 14 x3y3 15 - - - - byte4 x0y2 8 x1y2 9 x2y2 10 x3y2 11 - - - - byte3 x0y1 4 x1y1 5 x2y1 6 x3y1 7 - - - - b y te2 x0y0 0 x1y0 1 x2y0 2 x3y0 3 - - - - b y te1 b0 b1 b2 b3 b 4 b 5 b6 b7 byte 1 is the first returned byte in the sequence. in all the above examples a '1' in a bit position indicates that there is some type of error associated with the key. the use of the 'e' command (or 'e' with scope set to a specific key) will specify the nature of the error. k 0 x 6b - r eporting of f irst t ouched k ey 0 x 00..0xff 1 1 n/a get n/a n/a n/a n/a put return s #b y te s rtn d b y tes / cm d scop e section 2.11, p. 7 lowercase 'k'. returns a byte that indicates which (if any) key has been touched. the byte is structured as follows : k0 k1 k2 k3 - - - m b0 b1 b2 b3 b4 b5 b6 b7 bits are used as follows : m - if '1', indicates that yet another key is active k0..k3 - indicates the key number of a first detected key, in the range 0..15 (0x00..0x0f). if a reported key drops out while other keys are active, 'k' will report one of the other active keys, but there is no rule for which of the next keys gets reported in k0..k5. if the byte returned has a value of 255 (0xff), then no key has been detected. k 0x4b - key touch reporting for group 0x00..0xff 1 or 4 1 1, 4, 16 get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e section 2.11, p. 7 uppercase 'k'. returns 1 or 4 bytes depending on the current scope. the byte(s) returned contain a bit pattern which indicates touched keys. a scope of a single key, a row or a column will return one byte. a scope of all keys will return 4 bytes. the bitfields for a single key are : key - - - - - - - b0 b1 b2 b3 b4 b5 b6 b7 the bitfields for a single row (scope is x) are : y 0 y 1 y2 y3 - - - - b0 b1 b2 b3 b 4 b 5 b6 b7 the bitfields for a single column (scope is y) are : x0 x1 x2 x3 - - - - b0 b1 b2 b3 b4 b5 b6 b7 the bitfields for a global report are : x0y3 12 x1y3 13 x2y3 14 x3y3 15 - - - - byte4 x0y2 8 x1y2 9 x2y2 10 x3y2 11 - - - - byte3 x0y1 4 x1y1 5 x2y1 6 x3y1 7 - - - - b y te2 x0y0 0 x1y0 1 x2y0 2 x3y0 3 - - - - b y te1 b0 b1 b2 b3 b 4 b 5 b6 b7 byte 1 is the first returned byte in the sequence. in all the above examples a '1' in a bit position indicates that the key is touched; a '0' indicates no touch. ?quantum research group ltd. l q 20 www.qprox.com qt60161b / r1.03
5.4 setup commands setup functions are those that alter the behavior a key or a group of keys. the setups are programmed into eeprom locations in the part and ordinarily do not need to be reprogrammed once set. however it is possible to change a setup while the device is in normal operation without interrupting the sensing function of the part.24 setup functions alter the internal eeprom, and this requires a much longer time to complete than other commands; see table 4-1. setup 'put' commands become effective immediately after the echo response of the command byte unless otherwise noted; some setups require that the key(s) being altered be recalibrated with the 'b' command (page 24) before they take effect. ^a 0 x 01 - n egative d etect t hreshold 0x04..0x40 n/a 1 1 get 0x01 0x04..0x40 2 1, 4, 16 put returns byte 2 range bytes / cmd scope section 2.1, p. 5 ctrl-a. in put mode, the command followed by a setting is programmed into eeprom for the key(s) affected by scope. 1, 4, or 16 keys may be affected. valid decimal values are : 45678101215 17 20 25 30 35 45 55 64 values other than the above will be rounded down. in get mode, the command will return a single byte according to the current scope rules (section 5.2). this controls key sensitivity by setting the counts of signal delta needed to cause a detect. higher = less sensitive. numbers should be 6 or greater under most conditions to reduce the probability of noise detection. numbers greater than 20 indicate that the burst length is probably too high. this setup interacts with burst length (^f). ^b 0 x 02 - p ositive d etect t hreshold 0x04..0x40 n/a 1 1 get 0x02 0x04..0x40 2 1, 4, 16 put returns byte 2 range bytes / cmd scope section 2.2, p. 5 ctrl-b. in put mode, the command followed by a setting is programmed into eeprom for the key(s) affected by scope. 1, 4, or 16 keys may be affected. valid decimal values are : 45678101215 17 20 25 30 35 45 55 64 values other than the above will be rounded down. in get mode, the command will return a single byte according to the current scope rules (section 5.2). this setup controls the ability of a key to recalibrate quickly should the signal transition positive quickly, as when a touch is prolonged enough to cause a recalibration, and when the key is then 'untouched'. this condition can also be caused by a foreign object being removed from a key. the value should normally be set between 6 and 10 counts. if the value is very high, the key will still recover by means of the drift compensation process, albeit more slowly. ^c 0 x 03 - n egative t hreshold h ysteresis 0x01..0x03 n/a 1 16 get 0x03 0x01..0x03 2 16 put returns byte 2 range bytes / cmd scope section 2.3, p. 5 ctrl-c. in put mode, the command followed by a setting is programmed into eeprom for all keys only. the value should be from 0 to 3, representing hysteresis as follows : 0 : 50% 1 : 25% 2 : 12.5% 3 : 0% (no hysteresis) values other than the above will be rounded down. the percentage is the distance from the threshold level to the reference level. the hysteresis level is always closer to the threshold point than to the reference point. 25% is a reasonable value under most conditions. as this parameter is common to all keys, put and get operations send or return only one byte. ^d 0 x 04 - p ositive t hreshold h ysteresis 0x01..0x03 n/a 1 16 get 0x04 0x01..0x03 2 16 put return s b y te 2 ran ge b y tes / cm d scop e section 2.3, p. 5 ctrl-d. identical in operation to ^c above except this applies to positive 'detections' used to recalibrate the sensor (see ^b above for details). uses same hysteresis values as ^c above. ^f 0 x 06 - b urst l ength 0x00..0x40 n/a 1 1 get 0x06 0x00..0x40 2 1, 4, 16 put returns byte 2 range bytes / cmd scope section 3.5, p. 8 ctrl-f. in put mode the command sets the burst length of one or more keys, according to the current scope. valid decimal values are : 012345710 12 15 20 25 30 40 50 64 values other than the above will be rounded down. in get mode, the command will return a single byte according to the current scope rules (section 5.2). ^f sets the length of the acquisition burst on a key by key basis. this setting is directly proportional to signal gain. this setup interacts with negative and positive threshold (^a and ^b). increasing ^f can allow for higher threshold levels and more robust signals, at the expense of increased radiated emissions and reduced cx load capacity. special condition: if the value for ^f for a key is set to zero the burst disabled and the key will not function; the key will report back with an error code. the timing for the 'phantom burst' will be preserved so that overall key scan timing will remain unchanged. ?quantum research group ltd. l q 21 www.qprox.com qt60161b / r1.03
^g 0 x 07 - b urst s pacing 0x00..0x02 n/a 1 16 get 0x07 0x00..0x02 2 16 put return s b y te 2 ran ge b y tes / cm d scop e section 3.8, p. 9 ctrl-g. in put mode, sets the spacing between successive acquire bursts for the entire matrix. the second byte indicates the spacing to be set according to the following table : 0 : 500s (0.5ms) 1 : 1000s (1ms) 2 : 2000s (2ms) values higher than 2 will be truncated to 2. longer delay times equate to slower matrix scanning. at lower delay times (faster rep rates) there can be conflicts with long burst lengths and long conversion times which will prevent proper operation; see also section 3.6, and section 5.7. burst spacing also affects recalibration time; see section 2.10. the scope for this function is always 'all keys'. ^h 0 x 08 - n egative d rift c ompensation r ate 5 0x01..0x64 n/a 1 1 get 0x08 0x01..0x64 2 1, 4, 16 put returns byte 2 range bytes / cmd scope section 2.4, p. 5 ctrl-h. in put mode, sets the rate of drift compensation used during periods of non-detection, in the negative signal direction. valid decimal values are : 1234681012 15 20 25 33 45 60 75 100 values other than the above will be rounded down. these numbers correspond to the amount of drift compensation applied, in 100ms/count of reference change, for signals which are negative with respect to the reference level, i.e. in the same direction as legitimate detections. higher numbers equate to slower drift compensation. overcompensation (too fast) can result in the suppression of legitimate detections. under-compensation can result in inadequate compensation for rapid environmental changes. values of 15 to 45 (1.5 to 4.5 secs/count) are considered normal under most conditions. drift compensation does not occur while the signal has passed below the negative threshold level or subsequently remained below the negative hysteresis level. in get mode, the command will return a single byte according to the current scope rules (section 5.2). the scope in put mode can be one key, a row or column, or all keys. ^i 0 x 09 - p ositive d rift c ompensation r ate 0x01..0x64 n/a 1 1 get 0x09 0x01..0x64 2 1, 4, 16 put return s b y te 2 ran ge b y tes / cm d scop e section 2.4, p. 5 ctrl-i. same as ^h above in all respects, except operates only when the signal is positive with respect to the reference level, i.e. in an abnormal direction. it is usually desirable to set this rate much faster than for ^h, i.e. to a lower number. valid decimal values are : 1234681012 15 20 25 33 45 60 75 100 values other than the above will be rounded down. values of 4 to 10 (0.4 to 1.0 secs/count) are considered suitable for most systems. positive drift compensation continues to operate even if the signal has exceeded the positive threshold. ^j 0x0a - n egative d etect i ntegrator l imit 0x00..0xff n/a 1 1 get 0x0 a 0x00..0xff 2 1, 4, 16 put return s b y te 2 ran ge b y tes / cm d scop e section 2.6, p. 6 ctrl- j . in put mode, sets the detection integration limit for one or more keys according to scope. the unit of measure is a burst, i.e. a setting of 5 means that a detection must be sensed 5 bursts in sequence. a burst for a key occurs once every complete matrix scan. the second byte must be one of the following values (shown in decimal) : 0123571015 20 32 45 60 90 123 175 255 values other than the above will be rounded down. in get mode, the command will return a single byte according to the current scope rules (section 5.2). this setup can be used as a noise filter, or as a mechanism to intentionally slow down key reaction time in order to require a long user touch. special condition: if the value for ^ j is set to zero the key is disabled, but the burst for the key is still generated. ?quantum research group ltd. l q 22 www.qprox.com qt60161b / r1.03
^k 0x0b - p ositive r ecalibration d elay 0x00..0xff n/a 1 1 get 0x0b 0x00..0xff 2 1, 4, 16 put return s b y te 2 ran ge b y tes / cm d scop e section 2.7, p. 6 ctrl-k. in put mode, sets the delay until recalibration, timed from when the signal first crosses the positive threshold. the second byte controls the delay in 100ms increments, and must be one of the following valid values : 0123571015 20 32 45 60 90 123 175 255 values other than the above will be rounded down. as an example, a value of 60 will cause a 6-second delay. in get mode, the command will return a single byte according to the current scope rules (section 5.2). special condition: if ^k is set to zero this feature is disabled and the key will never auto-recalibrate on positive transitions; however drift compensation will still operate. ^l 0x0c - n egative r ecalibration d elay 0x00..0xff n/a 1 1 get 0x0c 0x00..0xff 2 1, 4, 16 put return s b y te 2 ran ge b y tes / cm d scop e section 2.5, p. 6 ctrl-l. in put mode, sets the delay until recalibration, timed from when the signal first crosses below the negative threshold as defined by ^a.2.5 the second byte represents the delay in 100ms increments, and must be one of the following valid values : 0123571015 20 32 45 60 90 123 175 255 values other than the above will be rounded down. as an example, a setting of 85 will cause delays of 6 seconds. in get mode the function returns a single value only; if scope is set to row, column, or all, only the value for the lowest ranking key in the group will be returned. special condition: if the value for ^l is set to zero this feature is disabled and the key will never auto-recalibrate after a prolonged touch. ^m 0x0d - i ntra -b urst p ulse s pacing 0x01..0x0a n/a 1 16 get 0x0d 0x01..0x0a 2 16 put return s b y te 2 ran ge b y tes / cm d scop e section 3.7, p. 9 ctrl-m. in put mode, sets the amount of time between individual pulses in a burst. the second byte must be in the range of 1 to 10 decimal; other values will be ignored. the setting applies to all keys. the value corresponds to the timing between pulses within a burst, in microseconds. for example, a setting of 5 will set the pulse spacing to 5 microseconds. in get mode the function returns the current value of ^m. intra-burst pulse spacing controls the fundamental frequency of the burst and can have a strong effect on radiated emissions from the matrix control panel. it can also have an effect on susceptibility to external emi if the external fields are close in periodicity to the burst spacing. ^n 0x0e - p ositive r eference e rror b and 0x00..0xff n/a 1 16 get 0x0e 0x00..0xff 2 16 put return s b y te 2 ran ge b y tes / cm d scop e section 2.8, p. 6 ctrl-n. in put mode, sets the amount of tolerable positive deviation in the reference level for all keys, in tenths of a percent, with regard to the 'locked' reference value for each key. the setup is global in nature and affects all keys equally. valid values are from 0 to 255 decimal. the percentage applied is one tenth the operand's decimal value. in get mode the function returns the current setting of ^n. this setup is used to define the limit of possible positive reference deviation with respect to a factory setting, which is used in turn to set an error flag for key(s) whose reference level rises above the designated error band. if for example this setting is set to 50, and the device is calibrated and reference levels are locked (see command 'l', lock reference levels, page 24) into the part by the oem, then in the future if the reference level of a key should rise 5% over its locked reference level then the key will report back an error flag via commands 'e' or 'e'. guardbands can be used to detect circuit faults as well as extremes of temperature or moisture on the circuitry. special condition: if the value is set to zero, this feature is disabled. ^o 0x0f - n egative r eference e rror b and 0x00..0xff n/a 1 16 get 0x0f 0x00..0xff 2 16 put return s b y te 2 ran ge b y tes / cm d scop e section 2.8, p. 6 ctrl-o. in put mode, sets the amount of tolerable negative deviation in the reference level for all keys, in tenths of a percent, with regard to the 'locked' reference value for each key. the setup is global in nature and affects all keys equally. valid values are from 0 to 255 decimal. the percentage applied is equal to the decimal value divided by 10, thus, a value of 20 equates to a 2% decrease (i.e. the lower boundary becomes 98% of the locked reference level). in get mode the function returns the current setting of ^m. this setup is identical in nature to ^n except that it governs negative reference deviations. special condition: if the value is set to 0, this feature is disabled. ?quantum research group ltd. l q 23 www.qprox.com qt60161b / r1.03
^p 0x10 - a djacent k ey s uppression (aks) 0x00, 0x01 n/a 1 1 get 0x10 0x00, 0x01 2 1, 4, 16 put return s b y te 2 ran ge b y tes / cm d scop e section 2.9, p. 6 ctrl-p. in put mode, instructs logic for the keys specified by the current scope to suppress a pending touch detection under certain signal conditions. valid 2nd byte values for this function are : 0 : aks off { default } 1 : aks on in get mode, the command will return a single byte according to the current scope rules (section 5.2). aks functions to suppress detections from water films which can 'spread' a touch signal from the touched key to adjacent keys. aks is also useful for panels with tightly spaced keys, where a fingertip can partially overlap an adjacent key. this feature will act to suppress the signals from the unintended key(s). aks only operates across keys that have been aks-enabled; signal strength comparisons are not made with non- aks-enabled keys. unused keys with burst lengths of zero are also ignored for purposes of aks. 5.5 supervisory / system functions supervisory functions report or control miscellaneous functions that affect overall chip control, testing, or diagnostics. all supervisory functions ignore scope except where noted. 6 0 x 36 - e eprom c hecksum 0 x 00..0xff 1 1 n/a get n/a n/a n/a n/a put returns # bytes rtnd bytes / cmd scope see page 18. l 0x4c - l ock r eference l evels n/a n/a n/a n/a get 0x4c 0x00 2 16 put returns 2nd byte bytes / cmd scope section 2.8, p. 6 uppercase 'l'. this is a put-only command that locks the reference levels of the device into eeprom for all keys, for boundary checking purposes over the product's life. the whole command C 'l' followed by a null (0x00) - must be received within 100ms without any intervening byte, or the command will fail. the part must be in put mode for this command to work. the scope of this command is always 'all keys'. this function records to eeprom the signal reference for all keys. the locked reference levels are used to compute boundary checks immediately after the command has finished. the results of this command to not take effect until the part has been reset. due to the large number of bytes written to eeprom by this command, there is a significant delay from the second byte until the return echo is sent back to the host. this command should be used only during production. there is no get version of the command. b 0x62 - r ecalibrate k eys n/a n/a n/a n/a get 0x62 n/a 1 1, 4, 16 put return s 2nd b y t e b y tes / cm d scop e section 2.10, p. 7; section 3.13. lowercase 'b'. this is a put-only command that causes the keys selected by scope to recalibrate. the part must be in put mode for this command to work. the return byte is sent before the keys have calibrated. while keys are in recalibration, status of the keys can be determined using the 'e' or 'e' commands. if 'b' is sent while key(s) are already in the middle of recalibration, the affected key(s) will abandon the old calibration cycle and start a new one. there is no get version of the command. ?quantum research group ltd. l q 24 www.qprox.com qt60161b / r1.03
l 0x6c - r eturn l ast c ommand c haracter 0x00..0xff 1 1 n/a get n/a n/a n/a n/a put return s # b y tes rtn d b y tes / cm d scop e lowercase 'l'. this get-only command reports back with the value of the prior command received by the part. the command also reports back any erroneous commands, allowing the host device to verify that a command was correctly received. if this command is repeated, the second and subsequent instances of 'l' will report back with 0x6c. there is no put version of the command. r 0x72 - r eset d evice n/a n/a n/a n/a get 0x72 0x00 2 n/a put return s 2nd b y t e b y tes / cm d scop e section 3.11, p. 9 lowercase 'r'. this put-only command hard-resets the part. the command 0x72 must be followed by a null (0x00) within 100ms or the command will fail. the part must be in put mode for this command to work. a reset occurs about 16ms after the echo byte 0x72 is transmitted back to the host. the part will resume communication and sensing in accordance with the timing shown in section 3.13. if for some reason the part is unable to send back the echo character 0x72, the command will fail. there is no get version of the command. v 0x56 - r eturn p art v ersion 0x00..0xff 1 1 n/a get n/a n/a n/a n/a put returns # bytes rtnd bytes / cmd scope uppercase 'v'. this get-only command returns the part version number. there is no put version of the command. w 0x57 - r eturn p art s ignature 0x10 1 1 n/a get n/a n/a n/a n/a put returns # bytes rtnd bytes / cmd scope uppercase 'w'. this get-only command returns the part signature as follows : 0x10 (16 decimal) there is no put version of this command. z 0x5a - e nter s leep n/a n/a n/a n/a get *0x5a, 0x5a 0x00 2 n/a put returns 2nd byte bytes / cmd scope section 3.14, p. 9 uppercase ' z '. this put-only command forces the device to enter sleep mode. the command 0x5a must be followed by a null (0x00) within 100ms or the command will fail. the part must be in put mode for this command to work. the command returns 0x5a immediately before going to sleep, and a second 0x5a upon waking up. if for some reason the device is unable to transmit the first return z character back to the host, for example due to the host not releasing the ss line, the part will completely reset after about 2 seconds. the part will reawaken after a logic low is detected for 10s on pin 11 (rst pin, see section 3.11). the device then sends a second z back to the host, and resumes from its prior state before it went to sleep without the need for recalibration. the device resumes in get mode only. there is no get version of the command. ^q 0x11 - d ata r ate s election 0x00..0x04 n/a 1 n/a get 0x11 0x00..0x04 2 n/a put return s 2nd b y te ran ge b y tes / cm d scop e section 4, p. 11 ctrl-q. this is a put-only command that sets the uart baud rate and the spi clock rate. all timings assume a 12mhz oscillator. the part must be in put mode for this command to work. spi settings - the acceptable values of the operand for spi use are : 0 : 93.75 khz 1 : 187.5 khz 2 : 750 khz 3 : 3 mhz these values define the maximum spi clock rate in master mode (part originates the clock). note that when the part is receiving data, the host can send to the device at rates up to 3mhz even if the rate setting of ^q is slower. refer to sections 4.3 and 4.4 for spi timing details. new settings do not become effective until the device has been powered off and back on again or after the reset ( ? r ? ) command. uart settings - the acceptable values of the operand for uart use are : 0 : 9600 baud 1 : 14400 baud 2 : 19200 baud 3 : 38400 baud 4 : 57600 baud there is no get version of this function. refer to section 4.5for uart details. new settings do not become effective until the device has been powered off and back on again or after the reset ( ? r ? ) command. ?quantum research group ltd. l q 25 www.qprox.com qt60161b / r1.03
^r 0x12 - o scilloscope s ync 0x00, 0x01 n/a 1 1, 4, 16 get 0x12 0x00, 0x01 2 1, 4, 16 put return s 2nd b y te ran ge b y tes / cm d scop e section 3.16, p. 11 ctrl-r. in put mode, controls the oscilloscope sync function of pin 43. the settings of this function are : 0 : off { factory default } 1 : on when on, pin 43 outputs a pulse that brackets the acquire burst(s) for the keys targeted by scope. without this it is virtually impossible to view signals on an oscilloscope corresponding to a specific key. pin 43 idles low and pulses high during a sync pulse. ^r is volatile, that is, it does not persist after a power down. ^w 0x17 - n oise s ync 0x00, 0x01 n/a 1 - get 0x17 0x00, 0x01 2 - put returns byte 2 range bytes / cmd scope section 3.14, p. 9 ctrl-w. in put mode, sets whether the noise sync feature is enabled or disabled. the part must be in put mode for this command to work. the settings are : 0 : off { factory default } 1 : on this function has global scope. the default value is 0 (off). in get mode this function returns the current setting of ^w. the setting of ^w does not become effective until the device has been powered off and back on again or after the reset ( ? r ? ) command has been issued. ?quantum research group ltd. l q 26 www.qprox.com qt60161b / r1.03
5.6 function summary table 20 - 0..0x0f 1, 4 1, 4, 16 g get indication of all touched keys report touches for group 0x4b k 20 - 0..0xff - - g get indication of first touched key report 1st key 0x6b k 20 - 0..0x0f 1, 4 1, 4, 16 g get error bits for group error codes for group 0x45 e 19 - 0..0x0f 1 1 g get error code for 1 key error code for 1 key 0x65 e 19 - 0..0xff 4, 16 4, 16 g get detection integrators for group det integrator for group 0x25 % 19 - 0..0xffff 8, 32 4, 16 g get references levels for group references for group 0x22 ? 19 - 0..0xff 4, 16 4, 16 g get reference-signal for group delta signals for group 0x21 ! 19 - 0..0xffff 8, 32 4, 16 g get signal for group signals for group 0x20 19 - 0..0x1f 1 - g get device status of entire device general device status 0x37 7 18 - 0..0xff 1 - g get eeprom checksum of entire eeprom eeprom checksum 0x36 6 18 - 0..0xff 1 1 g get detect integrator for 1 key det integrator for 1 key 0x35 0 18 - 0..0xffff 2 1 g get reference level for 1 key reference for 1 key 0x32 2 18 - 0..0xff 1 1 g get reference-signal for 1 key delta signal for 1 key 0x31 1 18 - 0..0xffff 2 1 g get signal strength for 1 key signal for 1 key 0x30 0 status commands 18 undefined 0x79 0x00..0x03 2 - p targets keys in a designated column, range 0..3 set column keys scope 0x79 y 18 undefined 0x78 0x00..0x03 2 - p targets keys in a designated row, range 0..3 set row keys scope 0x78 x 18 undefined 0x53 1 - p targets all keys in the matrix set all keys scope 0x53 s 18 undefined 0x73 0x00..0x0f 2 - p targets a specific key in range 0..15 set one key scope 0x73 s sco p e commands 17 get 0x70 1 - p all subsequent setup commands become 'puts? put 0x70 p 17 get 0x67 1 - p all subsequent setup commands become 'gets' get 0x67 g direction commands return range bytes returned scope returns operand range bytes/put scope page default setting get mode put mode p/g description name hex char ?quantum research group ltd. lq 27 www.qprox.com qt60161b / r1.03
24 0 (off) 0x00, 0x01 1 1 0x10 0x00, 0x01 2 1, 4, 16 p/g adjacent key suppression feature; 1 = on key suppression 0x10 ^p 23 0 (off) 0x00..0xff 1 16 0x0f 0x00..0xff 2 16 p/g tolerable ne g ative reference deviation with respect to locked reference values, step 0.1%. zero disables. neg error band 0x0f ^o 23 0 (off) 0x00..0xff 1 16 0x0e 0x00..0xff 2 16 p/g tolerable positive reference deviation with respect to locked reference values, step 0.1%. zero disables. pos error band 0x0e ^n 23 0x02 0x02..0x0a 1 64 0x0d 0x01..0x0a 2 16 p/g period of qt pulses, in microseconds 1, 2, 3, 4, 5, 6, 7, 8, 9, 10us intra-burst spacing 0x0d ^m 23 0x3c (9s) 0x00..0xff 1 1 0x0c 0x00..0xff 2 1, 8, 64 p/g time required to trigger a recal from a detection, in 0.1s increments. zero disables recal. 0, 0.1, 0.2, 0.3, 0.5, 0.7, 1.0, 1.5, 2.0, 3.2, 4.5, 6, 9, 12.3, 17.5, 25.5 secs neg recal delay 0x0c ^l 23 0x0a (1s) 0x00..0xff 1 1 0x0b 0x00..0xff 2 1, 4, 16 p/g time required to trigger a recal from a positive signal excursion in 0.1s increments; zero disables recal. 0, 0.1, 0.2, 0.3, 0.5, 0.7, 1.0, 1.5, 2.0, 3.2, 4.5, 6, 9, 12.3, 17.5, 25.5 secs pos recal delay 0x0b ^k 22 0x03 0x00..0xff 1 1 0x0a 0x00..0xff 2 1, 4, 16 p/g number of detections required to register a touch, counted in bursts of detection; zero disables a key. 0, 1, 2, 3, 5, 7, 10, 15, 20, 32, 45, 60, 90, 123, 175, 255 counts neg det int limit 0x0a ^j 22 0x0a (1s) 0x01..0x64 1 1 0x09 0x01..0x64 2 1, 4, 16 p/g rate of drift compensation for positive si g nal swin g s 0.1, 0.2, 0.3, 0.4, 0.6, 0.8, 1.0, 1.2, 1.5, 2.0, 2.5, 3.3, 4.5, 6.0, 7.5, 10 secs pos drift comp rate 0x09 ^i 22 0x1e (3s) 0x01..0x64 1 1 0x08 0x01..0x64 2 1, 4, 16 p/g rate of drift compensation for ne g ative si g nal swin g s 0.1, 0.2, 0.3, 0.4, 0.6, 0.8, 1.0, 1.2, 1.5, 2.0, 2.5, 3.3, 4.5, 6.0, 7.5, 10 secs neg drift comp rate 0x08 ^h 22 0 (500us) 0x00..0x02 1 16 0x07 0x00..0x02 2 16 p/g time from start of one burst to start of next burst 500us, 1ms, 2ms burst spacing 0x07 ^g 21 0x0c 0x01..0x40 1 1 0x06 0x00..0x40 2 1, 4, 16 p/g sets number of qt cycles / burst; zero disables burst 0, 1, 2, 3, 4, 5, 7, 10, 12, 15, 20, 25, 30, 40, 50, 64 burst length 0x06 ^f 21 0x01 (25%) 0x00..0x03 1 16 0x04 0x00..0x03 2 16 p/g hysteresis for positive threshold 50%, 25%, 12.5%, 0% positive hysteresis 0x04 ^d 21 0x01 (25%) 0x00..0x03 1 16 0x03 0x00..0x03 2 16 p/g hysteresis for negative threshold 50%, 25%, 12.5%, 0% negative hysteresis 0x03 ^c 21 0x08 0x04..0x40 1 1 0x02 0x04..0x40 2 1, 4, 16 p/g sensitivit y to positive si g nals for recalibration 4, 5, 6, 7, 8, 10, 12, 15, 17, 20, 25, 30, 35, 45, 55, 64 positive threshold 0x02 ^b 21 0x0c 0x04..0x40 1 1 0x01 0x04..0x40 2 1, 4, 16 p/g si g nal threshold; fewer counts = more sensitive 4, 5, 6, 7, 8, 10, 12, 15, 17, 20, 25, 30, 35, 45, 55, 64 negative threshold 0x01 ^a setu p commands return range bytes returned scope returns operand range bytes/put scope page default setting get mode put mode p/g description name hex char ?quantum research group ltd. lq 28 www.qprox.com qt60161b / r1.03
26 0 (off) 0x00, 0x01 1 - 0x17 0x00, 0x01 2 - g/p noise sync enable; 1 = on device must be reset to take effect noise sync 0x17 ^w 26 0 (off) 0x00, 0x01 1 - 0x12 0x00, 0x01 2 1, 4, 64 p/g oscilloscope sync control. 1 = on. feature is volatile - does not survive reset scope sync 0x12 ^r 25 0 (93.75k, 9600) 0x00..0x04 1 - 0x11 0x00..0x04 2 - p/g sets the master mode spi clock rate and uart rate; reset via ? r ? command or hard reset to take effect spi: 93.75khz, 187.5khz, 750khz, 3mhz uart: 9.6k, 14.4k, 19.2k, 38.4k, 57.6k data rate 0x11 ^q 25 - 0x5a, 0x5a 0x00 2 - p force device into sleep mode. ? z ? must be followed b y a null within 100ms. 0x5a returned before and after entering sleep sleep 0x5a z 25 - 0x10 1 - g returns part signature number signature 0x57 w 25 - 0x00..0xff 1 - g returns part version number version 0x56 v 25 - 0x72 0x00 2 - p hard reset the device. ? r ? must be followed by a null within 100ms. reset device 0x72 r 25 - 0x00..0xff 1 - g send back last command byte received return last command 0x6c l 24 - 0x62 1 1, 4, 16 p fully recalibrate keys; return byte is sent prior to calibration recal keys 0x62 b 24 - 0x4c 0x00 2 16 p locks reference levels into eeprom for future boundar y checks. ? l ? must be followed by 0x00 (null) 100ms after the command byte lock references 0x4c l 18 - 0x00..0xff 1 - g returns checksum of internal eeprom eeprom checksum 0x36 6 su p ervisor y commands return range bytes returned scope returns operand range bytes/put scope page default setting get mode put mode p/g description name hex char ?quantum research group ltd. lq 29 www.qprox.com qt60161b / r1.03
5.8 erratta / notes 4 april 2003 - the qt60xx5 version 1.05 datasheet erroneously showed negative recalibration timeouts in the range from 1..255 seconds. the correct range is 0.1..25.5 seconds. from datasheet version 1.06 on, this document change has been made. the devices themselves are not affected. 5.7 timing limitations the device requires processing time between bursts, as well as time to handle communications with the host. with short burst spacings, long burst lengths, and long intra-burst pulse spacings, the device can simply run out of available processing time. when this happens, burst timing and host communications slow down and become erratic. it is important that burst spacings be verified on an oscilloscope with an actual keymatrix during development to be certain that the device timings are preserved and are constant. if not, the burst length and/or pulse spacing should be reduced. ?quantum research group ltd. lq 30 www.qprox.com qt60161b / r1.03 table 5-2 permissible burst lengths (bl?s) cs = 4.7nf, cx = 5pf, rs = 180k ; 100s ramp time 64 2,000 64 2,000 64 2,000 64 2,000 40 1,000 40 1,000 50 1,000 50 1,000 20 500 20 500 25 500 30 500 max bl burst spacing max bl burst spacing max bl burst spacing max bl bu r st spacing pulse spacing = 10s pulse spacing = 9s pulse spacing = 8s pulse spacing = 7s 64 2,000 64 2,000 64 2,000 64 2,000 64 2,000 64 1,000 64 1,000 64 1,000 64 1,000 64 1,000 30 500 40 500 50 500 64 500 64 500 max bl burst spacing max bl burst spacing max bl burst spacing max bl burst spacing max bl burst spacing pulse spacin g = 6s pulse spacin g = 5s pulse spacin g = 4s pulse spacin g = 3s pulse spacin g = 2s
6 electrical specifications 6.1 absolute maximum specifications operating temp ....................................................................... -40 o c to +105 o c storage temp ......................................................................... -55 o c to +125 o c v dd ..................................................................................... -0.5 to +5.5v max continuous pin current, any control or drive pin ................................................. 10ma short circuit duration to ground, any pin ............................................................infinite short circuit duration to v dd , any pin .............................................................. infinite voltage forced onto any pin ..................................................... -0.6v to ( vdd + 0.6) volts frequency of operation ......................................................................... 16mhz eeprom maximum writes ............................................................ 100,000 write cycles 6.2 recommended operating conditions v dd ................................................................................... + 4.75 to 5.25v supply ripple+noise ....................................................................... 5mv p-p max cx transverse load capacitance per key .........................................................0 to 20pf fosc oscillator frequency .................................................................. 12mhz +/-2% 6.3 dc specifications vdd = 5.0v, cs = 4.7nf, freq = 12mhz, ta = recommended range, unless otherwise noted drdy, ss pins kohms 120 35 pullup resistors r p bits 16 10 acquisition resolution a r a 1 input leakage current i il 1ma source v vdd-0.7 high output voltage v oh 4ma sink v 0.6 low output voltage v ol v 2.2 high input logic level v hl v 0.8 low input logic level v il not including external components a 20 supply current, sleep i dds not including external components ma 25 supply current, running i ddr notes units max typ min description paramete r 6.4 protocol timing s 2,000 15 multi-byte return spacing t dr 3 s 1,000 1 tdr delay from response t dr 2 s 100 parallel port response delay t pr notes units max typ min description parameter ?quantum research group ltd. lq 31 www.qprox.com qt60161b / r1.03
6.5 maximum drdy response delays ... with adjacent key suppression disabled: 1ms 1ms 1.5ms all other commands 1ms 2ms 1.5ms get key errors (e), get keys pushed (k) 1.1ms 2ms 2ms calibrate command (all keys) 65ms 65ms 65ms lock reference level (l) 65ms 65ms 65ms setup - put (affect 16 keys) 20ms 20ms 20ms setup - put (affect 4 keys) 10ms 10ms 10ms setup - put (affect 1 key) 2ms 1ms 500s function type burst spacing ... with adjacent key suppression enabled: 1.1ms 2ms 1.5ms all other commands 1.1ms 2ms 2ms get key errors (e), get keys pushed (k) 1.2ms 2ms 2.5ms calibrate command (all keys) 65ms 65ms 65ms lock reference level (l) 65ms 65ms 65ms setup - put (affect 16 keys) 20ms 20ms 20ms setup - put (affect 4 keys) 10ms 10ms 10ms setup - put (affect 1 key) 2ms 1ms 500s function type burst spacing preliminary data: all specifications subject to change. ?quantum research group ltd. lq 32 www.qprox.com qt60161b / r1.03
7 mechanical 7.1 dimensions 7.2 marking ?quantum research group ltd. lq 33 www.qprox.com qt60161b / r1.03 1 2 3 4 8 7 6 5 11 10 9 33 32 31 30 28 23 24 25 26 27 29 12 14 16 18 22 20 15 17 19 21 13 44 42 40 38 36 34 43 41 37 39 35 symbol a e e h h l p p a millimeters inches min max notes min max notes e h h a e p a l o 12.21 11.75 0.458 0.478 0.09 0.20 0.003 0.008 0.45 0.05 0.75 0.15 1.20 0.018 0.002 0.030 0.006 0.047 0.80 0.30 bsc 8.00 0.80 0.45 0.031 0.012 bsc 0.315 0.031 0.018 9.90 10.10 0.386 0.394 - - o07 07 p bsc bsc sq sq sq sq package type: 44 pin tqfp 8.00 0.315 qt60161b-a QT60161B-AS -40 0 c to +105 0 c marking tqfp part number t a
8 index a adc, 8 adjacent key suppression, 6, 7, 12, 24, 28, 32 alert output led, 10, 11 application assistance, 4 b block diagram, 5 boundary limits, 19, 23, 29 burst length, 4, 7, 8, 9, 17, 21, 28, 30 burst spacing, 8, 9, 14, 22, 28, 30, 32 burst timing, 15, 30 c calibration recalibration, 5, 6, 7, 9, 10, 17, 19, 21, 23, 24, 29 circuit model, 7 cs, 5, 8, 9 d delta signals, 19, 27 detection integrator, 5, 6, 8, 18 direction commands, 17 drdy, 12 drift compensation, 5, 6, 11, 17, 21, 22, 23 dwell, 7, 9 e echo, 12, 13, 15, 21, 24 eeprom checksum, 18, 24 electrostatic shield, 11 emi, 11, 23 rfi, 8, 9, 21 error code, 4, 11, 16, 17, 19, 20, 21, 23 error guardbanding, 23 esd protection, 8, 9, 11 f field flow, 4, 8 function summary table, 27 g get command, 17 ground plane, 11 h hysteresis, 5, 21, 22 i intra-burst pulse spacing, 9, 23 k key design, 4 key numbering convention, 18 key reporting, 20 l led alert output, 10, 11 lock reference levels, 6, 14, 23, 24 m master mode, 12, 13 master-slave mode, 4, 12, 13 miso, 12, 13 mosi, 9, 12, 13 n negative detect integrator, 22 negative detect threshold, 21 negative drift compensation, 22 negative hysteresis, 5 negative recalibration delay, 6, 23 negative reference error band, 23 negative threshold, 5, 7, 8, 21, 22, 23 noise, 11, 12 noise filter, 22. see also emi o oscillator, 7, 9, 10, 12, 14, 25 oscilloscope sync, 11, 26 p pcb layout, 4, 11 positive detect threshold, 21 positive recalibration delay, 6, 7, 23 positive reference error band, 23 positive threshold, 5, 6, 7, 21, 23 power supply, 11 pulse spacing, 9, 23 put command, 17 q qmbtn, 4, 10, 11 r recalibrate keys (command), 24 recalibration calibration, 5, 6, 7, 9, 10, 17, 19, 21, 23, 24, 29 reset, 7, 9, 10, 11, 17, 25, 26 resonator, 7, 9. see also oscillator return last command, 25 ?quantum research group ltd. lq 34 www.qprox.com qt60161b / r1.03
return part signature, 25 rfi emi, 8, 9, 21 s slave mode, 13 sleep mode, 10 spi, 12, 15 spi noise problems, 11 t tcm, 12, 15 w water films, 24 x x-drives, 7, 8 ?quantum research group ltd. lq 35 www.qprox.com qt60161b / r1.03
l q copyright ? 2002 qrg ltd. all rights reserved. patented and patents pending corporate headquarters 1 mitchell point ensign way, hamble so31 4rf great britain tel: +44 (0)23 8056 5600 fax: +44 (0)23 8045 3939 admin@qprox.com www.qprox.com north america 651 holiday drive bldg. 5 / 300 pittsburgh, pa 15220 usa tel: 412-391-7367 fax: 412-291-1015 the specifications set out in this document are subject to change without notice. all products sold and services supplied by qr g are subject to our terms and conditions of sale and supply of services which are available online at www.qprox.com and are supplied with ev ery order acknowledgement. qprox, qtouch, qmatrix, qlevel, and qslide are trademarks of qrg. qrg products are not suitable for medical (including lifesaving equipment), safety or mission critical applications or other similar purposes. except as expressly set ou t in qrg's terms and conditions, no licenses to patents or other intellectual property of qrg (express or implied) are granted by qrg in connect ion with the sale of qrg products or provision of qrg services. qrg will not be liable for customer product design and customers are entirel y responsible for their products and applications which incorporate qrg's products.

▲Up To Search▲

Price & Availability of QT60161B-AS

	To Download QT60161B-AS Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .